CVE-2025-27206: Adobe Commerce · Improper Access Control
Affects Adobe CommerceSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 26 Oct 2026.
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
To mitigate this vulnerability, European organizations using Adobe Commerce should prioritize the following actions: 1) Monitor Adobe's official security advisories closely for patches or updates addressing CVE-2025-27206 and apply them promptly once available. 2) Implement strict network segmentation and firewall rules to limit external access to Adobe Commerce administrative interfaces and APIs, reducing exposure to remote attacks. 3) Employ Web Application Firewalls (WAFs) with custom rules to detect and block anomalous write requests or unauthorized access attempts targeting the e-commerce platform. 4) Conduct thorough access control audits within Adobe Commerce configurations to ensure least privilege principles are enforced and no unnecessary write permissions are granted to unauthenticated users or services. 5) Enhance logging and monitoring to detect unusual write operations or configuration changes, enabling rapid incident response. 6) Consider temporary compensating controls such as disabling non-essential features or endpoints that could be exploited until a patch is available. 7) Educate IT and security teams about this vulnerability to improve detection and response capabilities.
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 a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain limited write access. Exploitation of this issue does not require user interaction.