dbcve.org
CommerceApplication · Adobe

CVE-2025-27206

MEDIUM · 5.3 CVSS v3.1 Published 2025-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Adobe Commerce (formerly Magento) contains an Improper Access Control vulnerability allowing attackers to bypass security measures and gain limited write access without user interaction. The vulnerability affects versions 2.4.8, 2.4.7-p5, 2.4.6-p10, 2.4.5-p12, 2.4.4-p13 and earlier. This is a security feature bypass that could allow unauthorized modification of certain data or settings.

MitigationApply the vendor-provided security patch or upgrade to a patched version of Adobe Commerce. Review access control configurations and audit for any unauthorized changes following patch deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CommerceApplication
Affected:= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8
Commerce B2bApplication
Affected:= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.2
MagentoCMS
Affected:= 2.4.5= 2.4.6= 2.4.7= 2.4.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Adobe Commerce version
    Run the command 'php bin/magento --version' or check the file 'app/etc/env.php' for the version string under 'version' or 'system' > 'default' > 'commerce' settings
    Affected if The installed version matches 2.4.8, 2.4.7-p5, 2.4.6-p10, 2.4.5-p12, 2.4.4-p13 or earlier releases
  2. Verify Adobe Commerce B2B module status
    Run 'php bin/magento module:status Magento_B2b' or check composer.json for 'magento/module-b2b-core' version
    Affected if The B2B module is installed and enabled on versions 1.3.3, 1.3.4, 1.3.5, 1.4.2, 1.5.2 or earlier
  3. Review admin user accounts for unauthorized access
    Query the admin_user table or navigate to System > Permissions > All Users in the admin panel to list all admin accounts
    Affected if Unexpected or unauthorized admin user accounts exist that were not created by your authorized administrators
  4. Audit API integrations and integration tokens
    Check System > Extensions > Integrations or query the oauth_token table for any newly created or unfamiliar integration tokens
    Affected if Unrecognized integrations or tokens exist that were not configured by your security team
  5. Inspect access control role configurations
    Review System > Permissions > User Roles and compare against documented role definitions, or query the authorization_role table
    Affected if Roles have been modified to grant broader permissions than originally configured

You are affected if your Adobe Commerce installation runs a version within 2.4.4 through 2.4.8 (including patch versions) or your B2B module is at versions 1.3.3 through 1.5.2, and you observe unauthorized modifications to admin users, integrations, or role permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided security patch or upgrade to a patched version of Adobe Commerce. Review access control configurations and audit for any unauthorized changes following patch deployment.

Recommended fix High confidence

Upgrade to the latest patch version within your release line (2.4.4-p14+, 2.4.5-p13+, 2.4.6-p11+, 2.4.7-p6+, 2.4.8-p1+)

  1. 1. Identify your current Adobe Commerce version by running: bin/magento --version
  2. 2. Determine the appropriate upgrade path based on your current version
  3. 3. Backup your database and filesystem before upgrading
  4. 4. For Adobe Commerce 2.4.4: Upgrade to version 2.4.4-p14 or later
  5. 5. For Adobe Commerce 2.4.5: Upgrade to version 2.4.5-p13 or later
  6. 6. For Adobe Commerce 2.4.6: Upgrade to version 2.4.6-p11 or later
  7. 7. For Adobe Commerce 2.4.7: Upgrade to version 2.4.7-p6 or later
  8. 8. For Adobe Commerce 2.4.8: Upgrade to version 2.4.8-p1 or later
Caveat Minor patch upgrades typically have low risk but review Adobe's release notes for any breaking changes in the specific patch version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27206 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27206 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data