OpenMage vulnerable to XSS in Admin Notifications

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

4.6 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N · score source

EPSS

• CVE-2025-64174: 0.24% estimated exploitation activity in the next 30 days; percentile 14.77 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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/enUS/local.csv): 2. Flush Cache. Make sure locale is set to enUS. 3. Add any admin notification (e.g. via test.php) 4. Open Admin → System → Notifications → Inbox. 5. Profit. Impact The vulnerability is only exploitable by an attacker with administrative…

Published by the source

3 Nov 2025, 20:24 UTC

Last modified by the source

6 Nov 2025, 23:13 UTC

Source last checked

26 Oct 2026, 14:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qv78-c8hc-438r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-64174

Advisory: OpenMage vulnerable to XSS in Admin Notifications
IDs: CVE-2025-64174, GHSA-qv78-c8hc-438r
Record: https://patchnext.com/advisories/cve-2025-64174 (revision 1, source checked 26 Oct 2026, 14:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openmage/magento-lts 20.16.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist openmage/magento-lts: affected < 20.16.0; fixed in 20.16.0

## Suggested inspection (read-only)
- Packagist openmage/magento-lts: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openmage/magento-lts.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qv78-c8hc-438r (GitHub-reviewed advisory GHSA-qv78-c8hc-438r lists affected ranges: Packagist openmage/magento-lts >=0 <20.16.0)

Commands are suggestions: review each one before running it.