GHSA-GP6M-FQ6H-CJCX

OpenMage is affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low-privileged attacker to inject malicious scripts into vulnerable form fields.

Details

Mage_Adminhtml_Block_System_Config_Form_Field_File does not escape filename value in certain situations.
Same as: https://nvd.nist.gov/vuln/detail/CVE-2024-20717

PoC

1. Create empty file with this filename: <img src=x onerror=alert(1)>.crt
2. Go to System > Configuration > Sales | Payment Methonds.
3. Click Configure on PayPal Express Checkout.
4. Choose API Certificate from dropdown API Authentication Methods.
5. Choose the XSS-file and click Save Config.
6. Profit, alerts "1" -> XSS.
7. Reload, alerts "1" -> Stored XSS.

Affects admins that have access to any fileupload field in admin in core or custom implementations.
Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

GHSA-GP6M-FQ6H-CJCX has a CVSS score of 5.4 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (20.5.0, 19.5.3); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-GP6M-FQ6H-CJCX? GHSA-GP6M-FQ6H-CJCX is a medium-severity cross-site scripting (XSS) vulnerability in openmage/magento-lts (composer), affecting versions >= 20.0.0, < 20.5.0. It is fixed in 20.5.0, 19.5.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is GHSA-GP6M-FQ6H-CJCX? GHSA-GP6M-FQ6H-CJCX has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openmage/magento-lts are affected by GHSA-GP6M-FQ6H-CJCX? openmage/magento-lts (composer) versions >= 20.0.0, < 20.5.0 is affected.
4. Is there a fix for GHSA-GP6M-FQ6H-CJCX? Yes. GHSA-GP6M-FQ6H-CJCX is fixed in 20.5.0, 19.5.3. Upgrade to this version or later.
5. Is GHSA-GP6M-FQ6H-CJCX exploitable, and should I be worried? Whether GHSA-GP6M-FQ6H-CJCX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-GP6M-FQ6H-CJCX is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-GP6M-FQ6H-CJCX?
   • Upgrade openmage/magento-lts to 20.5.0 or later
   • Upgrade openmage/magento-lts to 19.5.3 or later