CVE-2025-64174

OpenMage versions v20.15.0 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by an admin with direct database access or the admin notification feed source to inject malicious scripts into vulnerable fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.

Details

Unescaped translation strings and URLs are printed into contexts inside app/code/core/Mage/Adminhtml/Block/Notification/Grid/Renderer/Actions.php. A malicious translation or polluted data can inject script.

• Link labels use __() without escaping.
• ’deleteConfirm()’ embeds a message without escaping.

PoC

1. Add XSS to admin locale (e.g. app/locale/en_US/local.csv):

   "Read Details","<img src=x onerror=alert(123)>"
   "Mark as Read","<script>alert(123)</script>"
   

2. Flush Cache. Make sure locale is set to en_US.
3. Add any admin notification (e.g. via test.php)

    <?php
    require 'app/Mage.php';
    Mage::app('admin');
    Mage::getModel('adminnotification/inbox')->setData([
      'severity'  => Mage_AdminNotification_Model_Inbox::SEVERITY_NOTICE,
      'date_added' => now(),
      'title' => 'XSS renderer test',
      'description' => 'Testing actions renderer',
      'url' => 'https://example.com', // makes the "Read Details" link appear
      'is_read' => 0, // makes the "Mark as Read" link appear
      'is_remove' => 0,
    ])->save();
   

4. Open Admin → System → Notifications → Inbox.
5. Profit.

The vulnerability is only exploitable by an attacker with administrative or translation privileges. Malicious JavaScript may be executed in a victim’s browser when they browse to the admin page containing the vulnerable fields.

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.

Kodem intelligence

1. What is CVE-2025-64174? CVE-2025-64174 is a medium-severity cross-site scripting (XSS) vulnerability in openmage/magento-lts (composer), affecting versions < 20.16.0. It is fixed in 20.16.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. Which versions of openmage/magento-lts are affected by CVE-2025-64174? openmage/magento-lts (composer) versions < 20.16.0 is affected.
3. Is there a fix for CVE-2025-64174? Yes. CVE-2025-64174 is fixed in 20.16.0. Upgrade to this version or later.
4. Is CVE-2025-64174 exploitable, and should I be worried? Whether CVE-2025-64174 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
5. What actually determines whether CVE-2025-64174 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.
6. How do I fix CVE-2025-64174? Upgrade openmage/magento-lts to 20.16.0 or later.