How severe is GHSA-vgmm-27fc-vmgp?

No CVSS score has been assigned to GHSA-vgmm-27fc-vmgp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vgmm-27fc-vmgp?

GHSA-vgmm-27fc-vmgp affects the following packages: mahocommerce/maho (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-vgmm-27fc-vmgp?

Update mahocommerce/maho to 25.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vgmm-27fc-vmgp is resolved across your whole dependency graph.

How do I detect GHSA-vgmm-27fc-vmgp in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mahocommerce/maho. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-vgmm-27fc-vmgp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-vgmm-27fc-vmgp?

O3 pinpoints whether GHSA-vgmm-27fc-vmgp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-vgmm-27fc-vmgp actively exploited in the wild?

No public exploit code has been indexed for GHSA-vgmm-27fc-vmgp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-vgmm-27fc-vmgp?

GHSA-vgmm-27fc-vmgp has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-vgmm-27fc-vmgp?

GHSA-vgmm-27fc-vmgp is classified as CWE-646 (CWE-646). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vgmm-27fc-vmgp published, and has it been updated?

GHSA-vgmm-27fc-vmgp was published on September 9, 2025 and was last updated on September 9, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-vgmm-27fc-vmgp

Maho is Vulnerable to Authenticated Remote Code Execution via File Upload

Also known asCVE-2025-58449

Published

Sep 9, 2025

Updated

Sep 9, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk20th percentile+0.09%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐘mahocommerce/maho

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.
<img width="648" height="194" alt="image" src="https://github.com/user-attachments/assets/1ab69182-68ea-48e4-b50b-46ccf70f40bb" />
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.
<img width="836" height="391" alt="image" src="https://github.com/user-attachments/assets/5abe7d80-c16d-4b54-9a19-799bda1bcc34" />
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.
<img width="473" height="286" alt="image" src="https://github.com/user-attachments/assets/326ce37e-026a-4211-8e95-6f5f310727df" />
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. <img width="910" height="339" alt="image" src="https://github.com/user-attachments/assets/e0e52607-81d5-4dc2-8550-ef324182f889" />

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 Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`mahocommerce/maho`	all versions	25.9.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mahocommerce/maho. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update mahocommerce/maho to 25.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vgmm-27fc-vmgp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-vgmm-27fc-vmgp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-vgmm-27fc-vmgp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 d

O3 Security · Impact-Aware SCA

Is GHSA-vgmm-27fc-vmgp in your dependencies?

O3 detects GHSA-vgmm-27fc-vmgp across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works