dbcve.org
CommerceApplication · Adobe

CVE-2025-27190

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-08
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.7-p4, 2.4.6-p9, 2.4.5-p11, 2.4.4-p12, 2.4.8-beta2 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 unauthorized 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 · high confidence

Adobe Commerce contains an Improper Access Control vulnerability allowing attackers to bypass security measures and gain unauthorized access to the application without any user interaction. The vulnerability affects multiple versions of the e-commerce platform and could allow security feature bypass.

MitigationApply the vendor-supplied patches for the affected Adobe Commerce versions (2.4.4-p12, 2.4.5-p11, 2.4.6-p9, 2.4.7-p4 and later). Verify access control configurations after patching to ensure the bypass vector is closed.

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.1
MagentoCMS
Affected:= 2.4.4= 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 installed Adobe Commerce version
    Run the CLI command to check the Magento application version, typically via bin/magento --version or by inspecting the composer.json file in the installation root
    Affected if The installed version is 2.4.4, 2.4.5, 2.4.6, 2.4.7, or 2.4.8 (all versions listed as affected)
  2. Identify installed Adobe Magento version
    If using Magento Open Source, check the version via bin/magento --version or composer.json
    Affected if The installed version is 2.4.4, 2.4.5, 2.4.6, 2.4.7, or 2.4.8 (all versions listed as affected)
  3. Check if B2B module is enabled
    Verify whether the Adobe Commerce B2B module is installed and enabled on the system, typically via bin/magento module:status or by checking module configuration files
    Affected if The B2B module is enabled and its version is 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.1
  4. Review access control configurations
    Inspect the ACL (Access Control List) settings and role permissions in the admin panel under System > Permissions > User Roles or via configuration files
    Affected if Any misconfigured or overly permissive ACL roles exist that could allow unauthorized access to protected resources

You are affected if your environment runs Adobe Commerce or Magento Open Source versions 2.4.4 through 2.4.8, or uses Adobe Commerce B2B versions 1.3.3 through 1.5.1, as all these versions contain the improper access control vulnerability.

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-supplied patches for the affected Adobe Commerce versions (2.4.4-p12, 2.4.5-p11, 2.4.6-p9, 2.4.7-p4 and later). Verify access control configurations after patching to ensure the bypass vector is closed.

Recommended fix Moderate confidence

Upgrade to the latest available patch release for your version line (2.4.4-p13+, 2.4.5-p12+, 2.4.6-p10+, 2.4.7-p5+) or to 2.4.8 stable when available

  1. 1. Identify your current Adobe Commerce or Magento 2 installation version using bin/magento --version or the admin panel.
  2. 2. For Adobe Commerce 2.4.4: Upgrade to version 2.4.4-p13 or later using composer require magento/product-community-edition=2.4.4-p13 --no-update followed by composer update.
  3. 3. For Adobe Commerce 2.4.5: Upgrade to version 2.4.5-p12 or later using composer require magento/product-community-edition=2.4.5-p12 --no-update followed by composer update.
  4. 4. For Adobe Commerce 2.4.6: Upgrade to version 2.4.6-p10 or later using composer require magento/product-community-edition=2.4.6-p10 --no-update followed by composer update.
  5. 5. For Adobe Commerce 2.4.7: Upgrade to version 2.4.7-p5 or later using composer require magento/product-community-edition=2.4.7-p5 --no-update followed by composer update.
  6. 6. After upgrade, clear the cache using bin/magento cache:flush and verify the new version with bin/magento --version.
Caveat Standard Adobe Commerce upgrade precautions apply - review compatibility with third-party extensions, back up database and files before upgrading, and test in a staging environment first

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

Fix this in Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27190 — 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-27190 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