Threats / Adobe / CVE-2025-54236
CVE-2025-54236
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Adobe Commerce and Magento vulnerability
Adobe Commerce and Magento Open Source contain an improper input validation flaw in the REST API that enables account takeover of customer accounts.
Verdict
Today item — known-exploited.
An unauthenticated attacker can exploit improper input validation in the Commerce REST API to compromise customer account credentials and gain unauthorized access to customer data and transaction history.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
114 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-10-24).
Probability (EPSS)
EPSS 0.96742 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Adobe, Commerce and Magento. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-20 Improper Input Validation.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft malicious input that bypasses validation checks in the REST API endpoint.
Business
Attackers gain a direct pathway to customer account compromise without requiring valid credentials.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I submit the crafted payload to take over an existing customer account through the API.
Business
Customer accounts are compromised, exposing personal information, payment methods, and order history to unauthorized parties.
3
Lateral reach — past segmentation narrative 3
Attacker
I access the compromised account to view sensitive customer data and transaction records.
Business
The organization faces data breach liability, regulatory fines, and mandatory breach notification costs.
4
Data at risk — exfiltration narrative 4
Attacker
I perform fraudulent transactions or modify account settings to maintain persistence.
Business
Revenue loss occurs through fraudulent orders and chargebacks, plus operational costs for incident response and remediation.
5
Lights out — disruption & extortion narrative 5
Attacker
I exfiltrate customer data for sale or use in further attacks against the customer base.
Business
Reputational damage, loss of customer trust, and potential class-action litigation result from widespread account compromise.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05