How severe is GHSA-xm9f-vxmx-4m58?

No CVSS score has been assigned to GHSA-xm9f-vxmx-4m58 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xm9f-vxmx-4m58?

GHSA-xm9f-vxmx-4m58 affects the following packages: openmage/magento-lts (Packagist), openmage/magento-lts (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-xm9f-vxmx-4m58?

Update openmage/magento-lts to 19.4.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xm9f-vxmx-4m58 is resolved across your whole dependency graph.

How do I detect GHSA-xm9f-vxmx-4m58 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openmage/magento-lts. 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-xm9f-vxmx-4m58 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-xm9f-vxmx-4m58?

O3 pinpoints whether GHSA-xm9f-vxmx-4m58 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-xm9f-vxmx-4m58 actively exploited in the wild?

No public exploit code has been indexed for GHSA-xm9f-vxmx-4m58 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 type of vulnerability is GHSA-xm9f-vxmx-4m58?

GHSA-xm9f-vxmx-4m58 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xm9f-vxmx-4m58 published, and has it been updated?

GHSA-xm9f-vxmx-4m58 was published on August 30, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-xm9f-vxmx-4m58

Fix: OpenMage/magento-lts@34709ac

GHSA-xm9f-vxmx-4m58 is a Improper Input Validation vulnerability in openmage/magento-lts. O3 Security confirms whether GHSA-xm9f-vxmx-4m58 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Data Flow Sanitation Issue Fix

Also known asCVE-2021-32759

Published

Aug 30, 2021

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘openmage/magento-lts🐘openmage/magento-lts

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

Impact

Due to missing sanitation in data flow it was possible for admin users to upload arbitrary executable files to the server.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`openmage/magento-lts`	all versions	19.4.15
🐘Packagist	`openmage/magento-lts`	≥ 20.0.0&&< 20.0.13	20.0.13

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openmage/magento-lts. 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 openmage/magento-lts to 19.4.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xm9f-vxmx-4m58 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-xm9f-vxmx-4m58 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-xm9f-vxmx-4m58. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Due to missing sanitation in data flow it was possible for admin users to upload arbitrary executable files to the server.

O3 Security · Impact-Aware SCA

Is GHSA-xm9f-vxmx-4m58 in your dependencies?

O3 detects GHSA-xm9f-vxmx-4m58 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