Magento Cross-Site Request Forgery (CSRF) vulnerability

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-49555: 0.96% estimated exploitation activity in the next 30 days; percentile 61.71 (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-alpha1, 2.4.8-p1, 2.4.7-p6, 2.4.6-p11, 2.4.5-p13, 2.4.4-p14 and earlier are affected by a Cross-Site Request Forgery (CSRF) vulnerability that could result in privilege escalation. A high-privileged attacker could trick a victim into executing unintended actions on a web application where the victim is authenticated, potentially allowing unauthorized access or modification of sensitive data. Exploitation of this issue requires user interaction in that a victim must visit a malicious website or click on a crafted link. Scope is changed.

Published by the source

12 Aug 2025, 18:31 UTC

Last modified by the source

22 Oct 2025, 20:55 UTC

Source last checked

26 Oct 2026, 14:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5777-jj7p-mpqw

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

# Patch Next advisory brief: CVE-2025-49555

Advisory: Magento Cross-Site Request Forgery (CSRF) vulnerability
IDs: CVE-2025-49555, GHSA-5777-jj7p-mpqw
Record: https://patchnext.com/advisories/cve-2025-49555 (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-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14. 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-alpha2; >= 2.4.8-beta1, < 2.4.8-p2; >= 2.4.7-beta1, < 2.4.7-p7; >= 2.4.6-p1, < 2.4.6-p12; < 2.4.5-p14; >= 2.4.5, <= 2.4.5; >= 2.4.6, <= 2.4.6; >= 2.4.7, <= 2.4.7; >= 2.4.8, <= 2.4.8; fixed in 2.4.7-p7, 2.4.8-p2, 2.4.6-p12, 2.4.5-p14, 2.4.9-alpha2

## 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-5777-jj7p-mpqw (GitHub-reviewed advisory GHSA-5777-jj7p-mpqw lists affected ranges: Packagist magento/project-community-edition >=0 =2.4.9-alpha1 =2.4.8-beta1 =2.4.7-beta1 =2.4.6-p1 =0 =2.4.5 =2.4.6 =2.4.7 =2.4.8 <=2.4.8)

Commands are suggestions: review each one before running it.