GHSA-9j5w-2cqc-cwj9 is a high-severity (CVSS 7.5) vulnerability in openmage/magento-lts. A fix is available for openmage/magento-lts — see the affected versions and patch details below.
Magento LTS vulnerable to Stored XSS via TinyMCE WYSIWYG Editor
Real-World Exposure
openmage/magento-ltsReal-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
From HackerOne report #1948040 by Halit AKAYDIN (hltakydn)
Impact
What kind of vulnerability is it? Who is impacted?
The TinyMCE WYSIWYG editor fails to filter scripts when rendering the HTML in specially crafted HTML tags.
Patches
Has the problem been patched? What versions should users upgrade to?
This vulnerability was fixed in version 20.2.0 by upgrading TinyMCE to a recent version in https://github.com/OpenMage/magento-lts/pull/3220
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
The WYSIWYG editor features could be disabled in the configuration. Possibly some WAF appliances would filter this attack.
References
Are there any links users can visit to find out more?
The attack is simply an exploit of the "onmouseover" attribute of an img element as described on OWASP XSS Filter Evasion
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | openmage/magento-lts | all versions | 20.2.0composer require openmage/magento-lts:^20.2.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openmage/magento-lts, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openmage/magento-lts to 20.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9j5w-2cqc-cwj9 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9j5w-2cqc-cwj9 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-9j5w-2cqc-cwj9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-9j5w-2cqc-cwj9 in your dependencies?
O3 Security finds GHSA-9j5w-2cqc-cwj9 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.