CVE-2025-43586: Adobe Commerce · Improper Access Control
Affects Adobe CommerceSource CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% 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 10 Jun 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Packagistadobe/commercepkg:composer/adobe/commerceOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Monitor Adobe’s official channels closely for the release of security patches addressing CVE-2025-43586 and apply them immediately upon availability. 2. Until patches are available, implement strict role-based access controls (RBAC) to limit the privileges of all users, minimizing the potential impact of privilege escalation. 3. Conduct thorough audits of user permissions and remove unnecessary privileges, especially for accounts with network access. 4. Enable detailed logging and monitoring of access control events and privilege changes to detect suspicious activities early. 5. Employ web application firewalls (WAFs) with custom rules to detect and block anomalous requests that may attempt to exploit access control weaknesses. 6. Restrict network access to the Adobe Commerce administrative interfaces to trusted IP addresses only. 7. Educate administrators and security teams about the vulnerability to ensure rapid response to any signs of exploitation. 8. Consider deploying intrusion detection systems (IDS) tuned to detect exploitation attempts targeting Adobe Commerce. 9. Regularly back up critical data and configurations to enable recovery in case of compromise.
Description
Adobe Commerce versions 2.4.8, 2.4.7-p5, 2.4.6-p10, 2.4.5-p12, 2.4.4-p13 and earlier are affected by an Improper Access Control vulnerability that could result in privilege escalation. A low privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized elevated access. Exploitation of this issue does not require user interaction.