dbcve.org
Commerce B2bApplication · Adobe

CVE-2025-27207

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
Remotely reachable 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 privilege escalation. A low privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized read 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 a low-privileged attacker to bypass security measures and gain unauthorized read access to sensitive data. The vulnerability stems from insufficient validation of user permissions on certain API endpoints or resources, enabling privilege escalation without user interaction.

MitigationApply the vendor-provided security patches for the affected versions (2.4.8, 2.4.7-p5, 2.4.6-p10, 2.4.5-p12, 2.4.4-p13) or upgrade to the latest patched release as specified in Adobe's security bulletin.

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
Commerce B2bApplication
Affected:= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 if Adobe Commerce B2b is installed
    Check the composer.json file or run: composer show adobe/commerce-b2b 2>/dev/null | grep -i version
    Affected if The adobe/commerce-b2b package is installed and the version matches 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.2 exactly
  2. Verify the B2B module is enabled
    Run: bin/magento module:status | grep -i b2b or check app/etc/config.php for Adobe_B2b module entry
    Affected if The B2B module is enabled and the version from step 1 is in the affected list
  3. Confirm API access controls exist for B2b endpoints
    Inspect etc/webapi.xml configuration files in the B2b module for permission definitions on company/user API endpoints
    Affected if API endpoints for company management or buyer resources lack proper authorization checks (the exact endpoints should be verified against Adobe's security bulletin)
  4. Check for shared company accounts or default permissions
    Review the B2b company configuration at Stores > Configuration > B2B Features > Company and examine whether default guest or shared accounts exist
    Affected if Multiple company users can access data from other company accounts or guest access is improperly configured

A user is affected if Adobe Commerce B2b is installed with version 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.2 and the B2B module is enabled, allowing low-privileged users to read sensitive data from other company accounts via unvalidated API endpoints.

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 patches for the affected versions (2.4.8, 2.4.7-p5, 2.4.6-p10, 2.4.5-p12, 2.4.4-p13) or upgrade to the latest patched release as specified in Adobe's security bulletin.

Recommended fix Moderate confidence

Adobe Commerce B2b 1.4.3 or later (or the next available patched release)

  1. 1. Review the Adobe Commerce B2B release notes and security patches for version 1.4.3 or later to confirm it contains the fix for CVE-2025-27207.
  2. 2. Create a full backup of the current Adobe Commerce B2b installation including database and files.
  3. 3. Test the upgrade in a staging environment that mirrors production configuration.
  4. 4. Apply the upgrade to the production environment following Adobe's standard upgrade procedures.
  5. 5. Verify the upgrade was successful and the version reflects the patched release.
  6. 6. Confirm the fix by reviewing the security patch documentation for this CVE.
Caveat Review Adobe Commerce upgrade documentation for potential breaking changes between 1.4.x versions; test thoroughly in non-production first

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

Fix this in Commerce B2b Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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