CVE-2025-24418: Adobe Commerce · Improper Authorization
Affects Adobe CommerceSource CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 26 Oct 2026, 09:08 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Feb 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Adobe Adobe Commerce | Affected
| Fixed in– |
AI-suggested
Organizations should immediately review and restrict user privileges within Adobe Commerce environments to the minimum necessary. Implement strict role-based access controls and audit authorization configurations to detect and prevent privilege escalation attempts. Monitor logs for unusual access patterns or privilege changes. Since no patches are currently available, consider deploying web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting authorization mechanisms. Engage with Adobe for updates and apply security patches as soon as they are released. Additionally, conduct penetration testing focused on authorization controls to identify and remediate weaknesses proactively. Segmentation of the e-commerce environment and limiting administrative access can further reduce risk exposure.
Description
Adobe Commerce versions 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier are affected by an Improper Authorization vulnerability that could result in Privilege escalation. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized access. Exploitation of this issue does not require user interaction.