Magento vulnerable to stored Cross-Site Scripting (XSS)

Exploitation

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

CVSS

8.1 · CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N

EPSS

• CVE-2025-54264: 0.60% estimated exploitation activity in the next 30 days; percentile 48.98 (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.

Magento versions 2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, 2.4.4-p15 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a high-privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality, and integrity impact to high. Exploitation of this issue requires user interaction in that a victim must browse to the page containing the vulnerable field. Scope is changed.

Published by the source

14 Oct 2025, 21:30 UTC

Last modified by the source

21 Oct 2025, 21:04 UTC

Source last checked

26 Oct 2026, 14:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2768-5wmv-cfff

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

# Patch Next advisory brief: CVE-2025-54264

Advisory: Magento vulnerable to stored Cross-Site Scripting (XSS)
IDs: CVE-2025-54264, GHSA-2768-5wmv-cfff
Record: https://patchnext.com/advisories/cve-2025-54264 (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: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: magento/community-edition 2.4.9-alpha3, 2.4.8-p3, 2.4.7-p8, 2.4.6-p13. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist magento/project-community-edition: affected <= 2.0.2
- Packagist magento/community-edition: affected >= 2.4.9-alpha1, < 2.4.9-alpha3; >= 2.4.8-beta1, < 2.4.8-p3; >= 2.4.7-beta1, < 2.4.7-p8; < 2.4.6-p13; >= 2.4.8, <= 2.4.8; >= 2.4.7, <= 2.4.7; >= 2.4.6, <= 2.4.6; fixed in 2.4.6-p13, 2.4.7-p8, 2.4.8-p3, 2.4.9-alpha3

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on magento/project-community-edition, magento/community-edition.
- 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-2768-5wmv-cfff (GitHub-reviewed advisory GHSA-2768-5wmv-cfff lists affected ranges: Packagist magento/project-community-edition >=0 =2.4.9-alpha1 =2.4.8-beta1 =2.4.7-beta1 =0 =2.4.8 =2.4.7 =2.4.6 <=2.4.6)

Commands are suggestions: review each one before running it.