dbcve.org
CommerceApplication · Adobe

CVE-2025-27191

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 1.3.3 / 2.4.4 or later.
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 versions 2.4.7-p4 and earlier contain an Improper Access Control vulnerability that allows attackers to bypass security measures and gain unauthorized access without user interaction. The vulnerability stems from insufficient access control enforcement in the Commerce platform, potentially allowing privilege escalation or unauthorized actions on protected resources.

MitigationApply the vendor-supplied security patch for this vulnerability to the affected Adobe Commerce installations. Verify the patch does not introduce regressions in authorization workflows and conduct security validation to confirm the bypass is no longer exploitable.

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.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8
Commerce B2bApplication
Affected:< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.1
MagentoCMS
Affected:< 2.4.4= 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 Adobe Commerce version
    Run the CLI command 'php bin/magento --version' from the Magento root directory, or check the 'composer.json' file for the 'version' property
    Affected if The installed version is 2.4.8, 2.4.7, 2.4.6, 2.4.5, 2.4.4, or any version below 2.4.4
  2. Identify Adobe Commerce B2B version
    Check the 'composer.json' file for 'adobe-commerce/b2b' package version, or run 'composer show adobe-commerce/b2b'
    Affected if The installed B2B version is 1.5.1, 1.4.2, 1.3.5, 1.3.4, 1.3.3, or any version below 1.3.3
  3. Identify Magento Open Source version
    Run 'php bin/magento --version' if using Magento Open Source, or check 'composer.json' for the metapackage version
    Affected if The installed version is 2.4.8, 2.4.7, 2.4.6, 2.4.5, 2.4.4, or any version below 2.4.4
  4. Check for existing security patches
    Review the 'app/etc/patchesApplied.txt' file or check for recently applied security-related patches in the codebase
    Affected if No specific patch for CVE-2025-27191 has been applied and the version falls within the affected range
  5. Verify admin access control configuration
    Review admin role permissions in the admin panel under System > Permissions > User Roles to ensure least-privilege principles are enforced
    Affected if The version is affected and broad permissions exist that could be exploited if the access control bypass is present

If the installed Adobe Commerce, Adobe Commerce B2b, or Magento Open Source version falls within the listed affected versions and no security patch has been applied, the environment is likely vulnerable to CVE-2025-27191.

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
Upgrade available Upgrade to 1.3.3 / 2.4.4 or later
Fixed in 1.3.32.4.4
Interim mitigation

Apply the vendor-supplied security patch for this vulnerability to the affected Adobe Commerce installations. Verify the patch does not introduce regressions in authorization workflows and conduct security validation to confirm the bypass is no longer exploitable.

Recommended fix High confidence

2.4.4-p12, 2.4.5-p11, 2.4.6-p9, or 2.4.7-p4 depending on your base version branch

  1. Identify your current Adobe Commerce or Magento version using the admin panel (System > Configuration > General > Advanced > Admin > Admin Base URL) or command line: php bin/magento --version
  2. For Adobe Commerce 2.4.4: Upgrade to security patch 2.4.4-p12 by running: composer require magento/product-community-edition=2.4.4-p12 --no-update && composer update
  3. For Adobe Commerce 2.4.5: Upgrade to security patch 2.4.5-p11 by running: composer require magento/product-community-edition=2.4.5-p11 --no-update && composer update
  4. For Adobe Commerce 2.4.6: Upgrade to security patch 2.4.6-p9 by running: composer require magento/product-community-edition=2.4.6-p9 --no-update && composer update
  5. For Adobe Commerce 2.4.7: Upgrade to security patch 2.4.7-p4 by running: composer require magento/product-community-edition=2.4.7-p4 --no-update && composer update
  6. Run composer update to install the patch
  7. Clear the Magento cache: php bin/magento cache:flush
  8. Re-deploy static content if needed: php bin/magento setup:static-content:deploy
Caveat Security patch upgrades are backward compatible; always test in a staging environment before production deployment

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

Fix this in Commerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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