IDORSSRFAUTH BYPASSJWT FORGERYRACE CONDITIONXXEBROKEN OBJECT-LEVEL AUTHPRIVILEGE ESCALATIONMASS ASSIGNMENTGRAPHQL INTROSPECTION ABUSEIDORSSRFAUTH BYPASSJWT FORGERYRACE CONDITIONXXEBROKEN OBJECT-LEVEL AUTHPRIVILEGE ESCALATIONMASS ASSIGNMENTGRAPHQL INTROSPECTION ABUSE
Impactr Logoimpactr
FeaturesHow it worksEvidencePricingLearnVulnerability DBCompare
  1. Home
  2. Vulnerability Database
  3. CVE-2025-54236
CVE-2025-54236 CISA KEV — actively exploited

Adobe Commerce and Magento Improper Input Validation Vulnerability

Adobe — Adobe Commerce

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. 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.

CVSS scoreCritical

9.1

EPSS — exploitation probabilityCritical

96.7%

Vector breakdown

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Published
Sep 9, 2025
Modified
Oct 24, 2025
Added to KEV
Oct 24, 2025
Federal patch due
Nov 14, 2025

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Weakness classification

CWE-20Improper Input Validation

Proof-of-concept & exploitation references

Weaponization

Nuclei template

Available

Metasploit module

Not found

Public repositories whose name or description references CVE-2025-54236, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.

No public GitHub repositories referencing CVE-2025-54236 were found at last check. Absence here is not proof no exploit exists - see the references below for vendor advisories and write-ups.

References

  • helpx.adobe.com

Frequently asked questions

What is CVE-2025-54236?

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. 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.

How severe is CVE-2025-54236?

CVE-2025-54236 has a CVSS base score of 9.1 out of 10 (CVSS 3.1).

Is CVE-2025-54236 actively exploited in the wild?

Yes. CVE-2025-54236 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Oct 24, 2025, meaning CISA has confirmed evidence of active exploitation.

What is the EPSS score for CVE-2025-54236?

96.7% - meaning FIRST.org's EPSS model estimates a 96.7% probability this vulnerability will be exploited in the wild within 30 days (100% percentile among all scored CVEs).

Is there exploit tooling available for CVE-2025-54236?

Yes - a public Nuclei template referencing CVE-2025-54236 exist in public repositories we checked.

What type of vulnerability is CVE-2025-54236?

CVE-2025-54236 is classified under CWE-20 (Improper Input Validation (CWE-20)).

Cross-checked against

  • NVD (NIST)
  • MITRE CVE Record
  • CISA KEV
  • FIRST.org EPSS
  • GitHub Advisory Database
  • GitHub public repository search

Impactr finds and proves whether CVE-2025-54236 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.

Join the waitlist
← Vulnerability database
Impactr Logoimpactr

Built by hackers, for the code you ship. Autonomous AI penetration testing for modern web apps and APIs.

© 2026 Impactr

Product

FeaturesCoverageUse casesEvidencePricingWaitlist

Resources

VulnerabilitiesVulnerability databaseGuidesComparisonsGlossaryCWE databaseBy industryBy languageHTTP status codesSecurity headers

Company

ContactTwitterLinkedInGitHub