CVE-2025-24411: Adobe Commerce · Improper Access Control
Affects Adobe CommerceSource CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 59% 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 inventory their Adobe Commerce deployments to identify affected versions. They should prioritize applying official patches from Adobe as soon as they are released. Until patches are available, implement network-level restrictions to limit access to Adobe Commerce administrative interfaces and APIs to trusted IP addresses only. Employ strict role-based access controls (RBAC) within Adobe Commerce to minimize privileges granted to users and services. Monitor logs and audit trails for unusual access patterns or privilege escalations. Use web application firewalls (WAFs) with updated signatures to detect and block exploitation attempts targeting this vulnerability. Conduct regular security assessments and penetration testing focused on access control mechanisms. Educate administrators about the risks of improper access control and enforce strong authentication methods, such as multi-factor authentication (MFA), to reduce the risk of credential compromise. Finally, maintain an incident response plan that includes procedures for handling potential breaches resulting from this vulnerability.
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 Access Control vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized access affecting Confidentiality and Integrity. Exploitation of this issue does not require user interaction.