Skip to content
vulnerability

CVE-2025-54236

9.1
Critical
KEV · Exploited in wildEPSS 95%Patch available

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.

exploited
Yes, in CISA KEV since 24 Oct 2025fix by 14 Nov 2025 (CISA deadline for US federal agencies)public exploit code
fix
Patch available see the advisory in the references
likelihood
EPSS 95.4%
Published 9 Sept 2025Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

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

triage
surface unknownruntimeWAF can block: partlyAV · networkCWE-20· Improper Input Validation

Can a WAF block it? Partly. Cloudflare publishes WAF rules written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.

Also consider: patch · enable the vendor rule in block mode

Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilitynone
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
common questions

Is CVE-2025-54236 being exploited?

Yes. CVE-2025-54236 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-54236?

CVE-2025-54236 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-54236?

Yes. A fix has been recorded for CVE-2025-54236. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-54236 affect?

CVE-2025-54236 affects adobe:commerce, adobe:commerce_b2b, adobe:magento. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
adobe:commerceadobe:commerce_b2badobe:magento
affected versions
Adobe Adobe Commerce
  • affected<= 2.4.4-p15

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Public exploit code: 1 Metasploit module · 7 GitHub proofs of concept · 1 Nuclei template

Metasploit
Nuclei

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
yes
technical impact
total

Assessed by CISA 24 Oct 2025 (SSVC 2.0.3).

timeline

  1. 9 Sept 2025Published
  2. 10 Sept 2025First public exploit or proof of concept · same day later
  3. 24 Oct 2025Added to CISA KEV (exploited in the wild) · 44 days later
  4. 24 Oct 2025CISA SSVC assessment: exploitation active · 1 day later
  5. 24 Oct 2025CVE record last updated · same day later
  6. 14 Nov 2025CISA remediation due date (US federal agencies) · 20 days later
  7. 2 Nov 2026Analysed by vulneraibility.com · 354 days (about 12 months) later

also known as

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
4 references in the CVE record: 1 advisory, 1 exploit, 1 mitigation, 1 link

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved