mahocommerce/maho

Version	Released
`26.9.0` minor	Sep 14, 2026
`26.7.5` patch	Aug 24, 2026
`26.7.4` patch	Aug 18, 2026
`26.7.3` patch	Aug 11, 2026
`26.7.2` patch	Aug 01, 2026
`26.7.1` patch	Jul 27, 2026
`26.7.0` minor	Jul 21, 2026
`26.5.0` minor	May 23, 2026
`26.3.0` minor	Mar 06, 2026
`26.1.0` major	Jan 13, 2026
`25.11.0` minor	Nov 01, 2025
`25.9.0` minor	Sep 07, 2025
`25.7.0` minor 1 CVE	Jul 19, 2025
`25.5.0` minor 1 CVE	May 12, 2025
`25.3.0` minor 1 CVE	Mar 14, 2025
`25.1.0` major 1 CVE	Jan 13, 2025
`24.11.0` minor 1 CVE	Nov 25, 2024
`24.9.0` initial 1 CVE	Sep 18, 2024

26.9.0 minor

Sep 14, 2026

26.7.5 patch

Aug 24, 2026

26.7.4 patch

Aug 18, 2026

26.7.3 patch

Aug 11, 2026

26.7.2 patch

Aug 01, 2026

26.7.1 patch

Jul 27, 2026

26.7.0 minor

Jul 21, 2026

26.5.0 minor

May 23, 2026

26.3.0 minor

Mar 06, 2026

26.1.0 major

Jan 13, 2026

25.11.0 minor

Nov 01, 2025

25.9.0 minor

Sep 07, 2025

25.7.0 minor

1 CVE

CVE-2025-58449 GHSA-vgmm-27fc-vmgp Sep 09, 2025

Maho is Vulnerable to Authenticated Remote Code Execution via File Upload

High

Network Low High

Summary

In Maho 25.7.0, an authenticated staff user with access to the Dashboard and Catalog\Manage Products permissions can create a custom option on a listing with a file input field. By allowing file uploads with a .php extension, the user can use the filed to upload malicious PHP files, gaining remote code execution

Details

An user with the Dashboard and Catalog\Manage Products permissions can abuse the product custom options feature to bypass the application’s file upload restrictions.

When creating a product custom option of type file upload, the user is allowed to define their own extension whitelist. This bypasses the application’s normal enforced whitelist and permits disallowed extensions, including .php.

The file uploaded by the custom option is then written to a predictable location:

/public/media/custom_options/<first char of filename>/<second char of filename>/<md5 of file contents>.php

Because this path is directly accessible under the application’s webroot, an attacker can then request the uploaded file via HTTP, causing the server to execute the PHP payload.

PoC

Sign in to the /admin dashboard as a staff user. Ensure the user's role has access to the Dashboard and Catalog\Manage Products permissions.
Navigate to a product catalog listing, for example by clicking on a product linked within the Most Viewed Products tab on the dashboard.

Navigate to the "Custom Options" tab on the product, and create a custom option with a file upload field. Add .php as an allowed extension to the file upload configuration. Save the configuration after making the changes.

In a private window, navigate to the customer facing page for the product, and upload a reverse shell PHP file through the newly configured option. Then click "Add to cart" to complete the upload.

Calculate the location of the uploaded file on the web server as

/public/media/custom_options/<first char of filename>/<second char of filename>/<md5 of file contents>.php

Navigate to the above path directly to execute the file contents and trigger the reverse shell.

Impact

This vulnerability allows remote code execution (RCE) on the server. It requires only the Catalog\Manage Products permission, and does not need full administrative access. By leveraging the custom option upload feature, an attacker can bypass the application’s normal file upload protections and execute arbitrary PHP code within the webroot.

Suggested Remediation

Enforce a whitelist of allowed extensions a user is allowed to configure for file upload fields in Custom Options.

Affected versions


          24.11.0


          24.9.0


          25.1.0


          25.3.0


          25.5.0


          25.7.0

Fixed in


          25.9.0

References

Updated Sep 10, 2026 · Source: OSV.dev

Jul 19, 2025

25.5.0 minor

1 CVE

CVE-2025-58449 GHSA-vgmm-27fc-vmgp Sep 09, 2025

Maho is Vulnerable to Authenticated Remote Code Execution via File Upload

High

Network Low High

Summary

In Maho 25.7.0, an authenticated staff user with access to the Dashboard and Catalog\Manage Products permissions can create a custom option on a listing with a file input field. By allowing file uploads with a .php extension, the user can use the filed to upload malicious PHP files, gaining remote code execution

Details

An user with the Dashboard and Catalog\Manage Products permissions can abuse the product custom options feature to bypass the application’s file upload restrictions.

When creating a product custom option of type file upload, the user is allowed to define their own extension whitelist. This bypasses the application’s normal enforced whitelist and permits disallowed extensions, including .php.

The file uploaded by the custom option is then written to a predictable location:

/public/media/custom_options/<first char of filename>/<second char of filename>/<md5 of file contents>.php

Because this path is directly accessible under the application’s webroot, an attacker can then request the uploaded file via HTTP, causing the server to execute the PHP payload.

PoC

Sign in to the /admin dashboard as a staff user. Ensure the user's role has access to the Dashboard and Catalog\Manage Products permissions.
Navigate to a product catalog listing, for example by clicking on a product linked within the Most Viewed Products tab on the dashboard.

Navigate to the "Custom Options" tab on the product, and create a custom option with a file upload field. Add .php as an allowed extension to the file upload configuration. Save the configuration after making the changes.

In a private window, navigate to the customer facing page for the product, and upload a reverse shell PHP file through the newly configured option. Then click "Add to cart" to complete the upload.

Calculate the location of the uploaded file on the web server as

/public/media/custom_options/<first char of filename>/<second char of filename>/<md5 of file contents>.php

Navigate to the above path directly to execute the file contents and trigger the reverse shell.

Impact

This vulnerability allows remote code execution (RCE) on the server. It requires only the Catalog\Manage Products permission, and does not need full administrative access. By leveraging the custom option upload feature, an attacker can bypass the application’s normal file upload protections and execute arbitrary PHP code within the webroot.

Suggested Remediation

Enforce a whitelist of allowed extensions a user is allowed to configure for file upload fields in Custom Options.

Affected versions


          24.11.0


          24.9.0


          25.1.0


          25.3.0


          25.5.0


          25.7.0

Fixed in


          25.9.0

References

Updated Sep 10, 2026 · Source: OSV.dev

May 12, 2025

25.3.0 minor

1 CVE

CVE-2025-58449 GHSA-vgmm-27fc-vmgp Sep 09, 2025

Maho is Vulnerable to Authenticated Remote Code Execution via File Upload

High

Network Low High

Summary

In Maho 25.7.0, an authenticated staff user with access to the Dashboard and Catalog\Manage Products permissions can create a custom option on a listing with a file input field. By allowing file uploads with a .php extension, the user can use the filed to upload malicious PHP files, gaining remote code execution

Details

An user with the Dashboard and Catalog\Manage Products permissions can abuse the product custom options feature to bypass the application’s file upload restrictions.

When creating a product custom option of type file upload, the user is allowed to define their own extension whitelist. This bypasses the application’s normal enforced whitelist and permits disallowed extensions, including .php.

The file uploaded by the custom option is then written to a predictable location:

/public/media/custom_options/<first char of filename>/<second char of filename>/<md5 of file contents>.php

Because this path is directly accessible under the application’s webroot, an attacker can then request the uploaded file via HTTP, causing the server to execute the PHP payload.

PoC

Sign in to the /admin dashboard as a staff user. Ensure the user's role has access to the Dashboard and Catalog\Manage Products permissions.
Navigate to a product catalog listing, for example by clicking on a product linked within the Most Viewed Products tab on the dashboard.

Navigate to the "Custom Options" tab on the product, and create a custom option with a file upload field. Add .php as an allowed extension to the file upload configuration. Save the configuration after making the changes.

In a private window, navigate to the customer facing page for the product, and upload a reverse shell PHP file through the newly configured option. Then click "Add to cart" to complete the upload.

Calculate the location of the uploaded file on the web server as

/public/media/custom_options/<first char of filename>/<second char of filename>/<md5 of file contents>.php

Navigate to the above path directly to execute the file contents and trigger the reverse shell.

Impact

This vulnerability allows remote code execution (RCE) on the server. It requires only the Catalog\Manage Products permission, and does not need full administrative access. By leveraging the custom option upload feature, an attacker can bypass the application’s normal file upload protections and execute arbitrary PHP code within the webroot.

Suggested Remediation

Enforce a whitelist of allowed extensions a user is allowed to configure for file upload fields in Custom Options.

Affected versions


          24.11.0


          24.9.0


          25.1.0


          25.3.0


          25.5.0


          25.7.0

Fixed in


          25.9.0

References

Updated Sep 10, 2026 · Source: OSV.dev

Mar 14, 2025

25.1.0 major

1 CVE

CVE-2025-58449 GHSA-vgmm-27fc-vmgp Sep 09, 2025

Maho is Vulnerable to Authenticated Remote Code Execution via File Upload

High

Network Low High

Summary

In Maho 25.7.0, an authenticated staff user with access to the Dashboard and Catalog\Manage Products permissions can create a custom option on a listing with a file input field. By allowing file uploads with a .php extension, the user can use the filed to upload malicious PHP files, gaining remote code execution

Details

An user with the Dashboard and Catalog\Manage Products permissions can abuse the product custom options feature to bypass the application’s file upload restrictions.

When creating a product custom option of type file upload, the user is allowed to define their own extension whitelist. This bypasses the application’s normal enforced whitelist and permits disallowed extensions, including .php.

The file uploaded by the custom option is then written to a predictable location:

/public/media/custom_options/<first char of filename>/<second char of filename>/<md5 of file contents>.php

Because this path is directly accessible under the application’s webroot, an attacker can then request the uploaded file via HTTP, causing the server to execute the PHP payload.

PoC

Sign in to the /admin dashboard as a staff user. Ensure the user's role has access to the Dashboard and Catalog\Manage Products permissions.
Navigate to a product catalog listing, for example by clicking on a product linked within the Most Viewed Products tab on the dashboard.

Navigate to the "Custom Options" tab on the product, and create a custom option with a file upload field. Add .php as an allowed extension to the file upload configuration. Save the configuration after making the changes.

In a private window, navigate to the customer facing page for the product, and upload a reverse shell PHP file through the newly configured option. Then click "Add to cart" to complete the upload.

Calculate the location of the uploaded file on the web server as

/public/media/custom_options/<first char of filename>/<second char of filename>/<md5 of file contents>.php

Navigate to the above path directly to execute the file contents and trigger the reverse shell.

Impact

This vulnerability allows remote code execution (RCE) on the server. It requires only the Catalog\Manage Products permission, and does not need full administrative access. By leveraging the custom option upload feature, an attacker can bypass the application’s normal file upload protections and execute arbitrary PHP code within the webroot.

Suggested Remediation

Enforce a whitelist of allowed extensions a user is allowed to configure for file upload fields in Custom Options.

Affected versions


          24.11.0


          24.9.0


          25.1.0


          25.3.0


          25.5.0


          25.7.0

Fixed in


          25.9.0

References

Updated Sep 10, 2026 · Source: OSV.dev

Jan 13, 2025

24.11.0 minor

1 CVE

CVE-2025-58449 GHSA-vgmm-27fc-vmgp Sep 09, 2025

Maho is Vulnerable to Authenticated Remote Code Execution via File Upload

High

Network Low High

Summary

In Maho 25.7.0, an authenticated staff user with access to the Dashboard and Catalog\Manage Products permissions can create a custom option on a listing with a file input field. By allowing file uploads with a .php extension, the user can use the filed to upload malicious PHP files, gaining remote code execution

Details

An user with the Dashboard and Catalog\Manage Products permissions can abuse the product custom options feature to bypass the application’s file upload restrictions.

When creating a product custom option of type file upload, the user is allowed to define their own extension whitelist. This bypasses the application’s normal enforced whitelist and permits disallowed extensions, including .php.

The file uploaded by the custom option is then written to a predictable location:

/public/media/custom_options/<first char of filename>/<second char of filename>/<md5 of file contents>.php

Because this path is directly accessible under the application’s webroot, an attacker can then request the uploaded file via HTTP, causing the server to execute the PHP payload.

PoC

Sign in to the /admin dashboard as a staff user. Ensure the user's role has access to the Dashboard and Catalog\Manage Products permissions.
Navigate to a product catalog listing, for example by clicking on a product linked within the Most Viewed Products tab on the dashboard.

Navigate to the "Custom Options" tab on the product, and create a custom option with a file upload field. Add .php as an allowed extension to the file upload configuration. Save the configuration after making the changes.

In a private window, navigate to the customer facing page for the product, and upload a reverse shell PHP file through the newly configured option. Then click "Add to cart" to complete the upload.

Calculate the location of the uploaded file on the web server as

/public/media/custom_options/<first char of filename>/<second char of filename>/<md5 of file contents>.php

Navigate to the above path directly to execute the file contents and trigger the reverse shell.

Impact

This vulnerability allows remote code execution (RCE) on the server. It requires only the Catalog\Manage Products permission, and does not need full administrative access. By leveraging the custom option upload feature, an attacker can bypass the application’s normal file upload protections and execute arbitrary PHP code within the webroot.

Suggested Remediation

Enforce a whitelist of allowed extensions a user is allowed to configure for file upload fields in Custom Options.

Affected versions


          24.11.0


          24.9.0


          25.1.0


          25.3.0


          25.5.0


          25.7.0

Fixed in


          25.9.0

References

Updated Sep 10, 2026 · Source: OSV.dev

Nov 25, 2024

24.9.0 initial

1 CVE

CVE-2025-58449 GHSA-vgmm-27fc-vmgp Sep 09, 2025

Maho is Vulnerable to Authenticated Remote Code Execution via File Upload

High

Network Low High

Summary

In Maho 25.7.0, an authenticated staff user with access to the Dashboard and Catalog\Manage Products permissions can create a custom option on a listing with a file input field. By allowing file uploads with a .php extension, the user can use the filed to upload malicious PHP files, gaining remote code execution

Details

An user with the Dashboard and Catalog\Manage Products permissions can abuse the product custom options feature to bypass the application’s file upload restrictions.

When creating a product custom option of type file upload, the user is allowed to define their own extension whitelist. This bypasses the application’s normal enforced whitelist and permits disallowed extensions, including .php.

The file uploaded by the custom option is then written to a predictable location:

/public/media/custom_options/<first char of filename>/<second char of filename>/<md5 of file contents>.php

Because this path is directly accessible under the application’s webroot, an attacker can then request the uploaded file via HTTP, causing the server to execute the PHP payload.

PoC

Sign in to the /admin dashboard as a staff user. Ensure the user's role has access to the Dashboard and Catalog\Manage Products permissions.
Navigate to a product catalog listing, for example by clicking on a product linked within the Most Viewed Products tab on the dashboard.

Navigate to the "Custom Options" tab on the product, and create a custom option with a file upload field. Add .php as an allowed extension to the file upload configuration. Save the configuration after making the changes.

In a private window, navigate to the customer facing page for the product, and upload a reverse shell PHP file through the newly configured option. Then click "Add to cart" to complete the upload.

Calculate the location of the uploaded file on the web server as

/public/media/custom_options/<first char of filename>/<second char of filename>/<md5 of file contents>.php

Navigate to the above path directly to execute the file contents and trigger the reverse shell.

Impact

This vulnerability allows remote code execution (RCE) on the server. It requires only the Catalog\Manage Products permission, and does not need full administrative access. By leveraging the custom option upload feature, an attacker can bypass the application’s normal file upload protections and execute arbitrary PHP code within the webroot.

Suggested Remediation

Enforce a whitelist of allowed extensions a user is allowed to configure for file upload fields in Custom Options.

Affected versions


          24.11.0


          24.9.0


          25.1.0


          25.3.0


          25.5.0


          25.7.0

Fixed in


          25.9.0

References

Updated Sep 10, 2026 · Source: OSV.dev

Sep 18, 2024

Activity

Reach

Details

Summary

Details

PoC

Impact

Suggested Remediation

Summary

Details

PoC

Impact

Suggested Remediation

Summary

Details

PoC

Impact

Suggested Remediation

Summary

Details

PoC

Impact

Suggested Remediation

Summary

Details

PoC

Impact

Suggested Remediation

Summary

Details

PoC

Impact

Suggested Remediation

Summary

Details

PoC

Impact

Suggested Remediation