dbcve.org
CommerceApplication · Adobe

CVE-2022-34255

HIGH · 8.8 CVSS v3.1 Published 2022-08-16
Fix available
A fix is available. Upgrade to 2.3.7 / 2.4.3 or later.
See remediation →
94/100
Remediation priority · Urgent
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.3-p2 (and earlier), 2.3.7-p3 (and earlier) and 2.4.4 (and earlier) are affected by an Improper Access Control vulnerability that could result in Privilege escalation. An attacker with a low privilege account could leverage this vulnerability to perform an account takeover for a victim. 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

Improper Access Control vulnerability in Adobe Commerce allows authenticated low-privilege users to perform account takeover via privilege escalation. The attacker can leverage their existing account to take over higher-privilege user accounts without any user interaction.

MitigationApply Adobe's official security patches for this vulnerability (SUPEE-11937 for 2.3.x or corresponding patches for 2.4.x), or upgrade to a patched version of Adobe Commerce (2.4.4-p1 or later, 2.4.3-p3 or later, 2.3.7-p4 or later).

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.3.0, < 2.3.7>= 2.4.0, < 2.4.3= 2.3.7= 2.4.3= 2.4.4
MagentoCMS
Affected:>= 2.3.0, < 2.3.7>= 2.4.0, < 2.4.3= 2.3.7= 2.4.3= 2.4.4

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
High
Availability
High

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

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 the installed Adobe Commerce or Magento version
    Run the command: php bin/magento --version OR check the composer.json file in the installation root for the magento/product-community-edition or magento/product-enterprise-edition version
    Affected if The installed version is 2.3.0 through 2.3.7 (any), 2.4.0 through 2.4.3 (any), or exactly 2.4.4
  2. Verify user registration is enabled
    Navigate to Admin Panel > Customers > Configuration > Customer Configuration > Account Creation Options and check if 'Allow Customer to Register' is set to Yes, or inspect the core_config_data table for path 'customer/create_account/disabled' with value '0'
    Affected if Customer registration is enabled, allowing new low-privilege user accounts to be created
  3. Check for existing low-privilege customer accounts
    Query the customer_entity table in the database: SELECT COUNT(*) FROM customer_entity WHERE group_id != 1 (assuming group_id 1 is the default customer group); or inspect customer accounts in Admin Panel > Customers > All Customers
    Affected if There are existing customer accounts (non-admin users) in the system that could be exploited for privilege escalation
  4. Verify admin user management configuration
    Review Admin Panel > System > Permissions > Users to confirm the presence of admin accounts that could be targeted for takeover via the vulnerability
    Affected if Admin-level user accounts exist in the system that could be compromised through the privilege escalation flaw

The environment is affected if the Adobe Commerce/Magento version falls within 2.3.0-2.3.7, 2.4.0-2.4.3, or 2.4.4 AND the application has enabled customer registration or already has low-privilege user accounts present alongside admin accounts.

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 2.3.7 / 2.4.3 or later
Fixed in 2.3.72.4.3
Interim mitigation

Apply Adobe's official security patches for this vulnerability (SUPEE-11937 for 2.3.x or corresponding patches for 2.4.x), or upgrade to a patched version of Adobe Commerce (2.4.4-p1 or later, 2.4.3-p3 or later, 2.3.7-p4 or later).

Recommended fix High confidence

Adobe Commerce/Magento 2.4.4 or later (2.4.x line); 2.3.7-p3 or later (2.3.x line)

  1. 1. Back up the current Adobe Commerce/Magento database and files
  2. 2. Review the Adobe Commerce 2.4.4 or 2.3.7-p3 release notes for any compatibility notes
  3. 3. Run composer require magento/product-community-edition=2.4.4 --no-update (or appropriate version) for 2.4.x installations
  4. 4. Run composer update to fetch the new packages
  5. 5. Run bin/magento setup:upgrade to apply database migrations
  6. 6. Run bin/magento cache:flush to clear caches
  7. 7. Verify the upgrade was successful and test critical functionality
Caveat Review Adobe's upgrade compatibility notes - some extensions or customizations may require updates for compatibility with the new version

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

Fix this in Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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