Magento Community Edition Improper Input Validation vulnerability

Exploitation

Confirmed: listed in the CISA Known Exploited Vulnerabilities catalog.

CVSS

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

EPSS

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

Adobe Commerce 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 an Improper Input Validation vulnerability that could result in a Security feature bypass. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality and integrity impact to high. Exploitation of this issue does not require user interaction.

Published by the source

9 Sep 2025, 15:31 UTC

Last modified by the source

27 Oct 2025, 15:13 UTC

Source last checked

26 Oct 2026, 14:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wh92-6q6g-px7j

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

# Patch Next advisory brief: CVE-2025-54236

Advisory: Magento Community Edition Improper Input Validation vulnerability
IDs: CVE-2025-54236, GHSA-wh92-6q6g-px7j
Record: https://patchnext.com/advisories/cve-2025-54236 (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: Critical (CVSS 9.1)
Exploitation: confirmed: listed in the CISA Known Exploited Vulnerabilities catalog.
Vendor response: Vendor response not established. 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.5-p14; >= 2.4.6, <= 2.4.6; >= 2.4.6-p1, <= 2.4.6-p12; >= 2.4.5, <= 2.4.5; >= 2.4.9-alpha1, <= 2.4.9-alpha2; >= 2.4.7, <= 2.4.7; >= 2.4.8, <= 2.4.8; >= 2.4.7-beta1, <= 2.4.7-p7; >= 2.4.8-beta1, <= 2.4.8-p2; >= 2.4.9, <= 2.4.9

## 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?
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://www.cisa.gov/known-exploited-vulnerabilities-catalog (CISA added CVE-2025-54236 to the Known Exploited Vulnerabilities catalog on 2025-10-24.)
- Verified: https://github.com/advisories/GHSA-wh92-6q6g-px7j (GitHub-reviewed advisory GHSA-wh92-6q6g-px7j lists affected ranges: Packagist magento/community-edition >=0 =2.4.6 =2.4.6-p1 =2.4.5 =2.4.9-alpha1 =2.4.7 =2.4.8 =2.4.7-beta1 =2.4.8-beta1 =2.4.9 =0 <=2.0.2)

Commands are suggestions: review each one before running it.