dbcve.org
CommerceApplication · Adobe

CVE-2022-42344

HIGH · 8.8 CVSS v3.1 Published 2022-10-20
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 Incorrect Authorization vulnerability. An authenticated attacker can exploit this vulnerability to achieve information exposure and privilege escalation.

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.3-p2 and earlier, 2.3.7-p3 and earlier, and 2.4.4 and earlier contain an incorrect authorization vulnerability that allows authenticated attackers with standard user accounts to bypass access controls, leading to information exposure and privilege escalation to administrative levels.

MitigationApply the vendor-supplied security patch or upgrade to Adobe Commerce 2.4.3-p3, 2.3.7-p4, or 2.4.5 or later to remediate this authorization bypass.

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.7>= 2.4.0, < 2.4.3= 2.3.7= 2.4.3= 2.4.4
MagentoCMS
Affected:< 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 installed Adobe Commerce or Magento version
    Run the CLI command: php bin/magento --version or check the composer.json file in the project root for the version entry under 'require' (e.g., 'magento/product-community-edition')
    Affected if The version is 2.4.4, or 2.4.3-p2 or earlier, or 2.3.7-p3 or earlier, or any version before 2.3.7
  2. Confirm vendor product type
    Check if the installation is Adobe Commerce (original vendor) or Magento Open Source by reviewing the composer.json package name (magento/project-enterprise-edition for Adobe Commerce, magento/project-community-edition for Magento)
    Affected if The product is Adobe Commerce or Magento (any edition) and the version falls within the affected ranges in step 1
  3. Verify user authentication is enabled
    Check the admin configuration at Stores > Settings > Configuration > Advanced > Admin > Admin Base URLs, or inspect the etc/env.php file for admin frontName to confirm the admin panel is accessible
    Affected if The admin panel is accessible and user authentication is enabled, which is required for the authenticated attacker to exploit the bypass
  4. Review user role permissions for privilege escalation indicators
    Navigate to System > Permissions > User Roles in the admin panel, or query the authorization_role and authorization_rule tables in the database to identify any standard user roles that have been granted elevated permissions beyond their intended scope
    Affected if Standard (non-admin) user roles exist with permissions that exceed normal user-level access, indicating possible exploitation or misconfiguration

A user is affected if they run Adobe Commerce or Magento version 2.4.4, 2.4.3-p2 or earlier, 2.3.7-p3 or earlier, or any version before 2.3.7, and the admin panel with user authentication is accessible.

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 the vendor-supplied security patch or upgrade to Adobe Commerce 2.4.3-p3, 2.3.7-p4, or 2.4.5 or later to remediate this authorization bypass.

Recommended fix High confidence

Adobe Commerce/Magento OpenSource 2.4.5+ or 2.3.7-p4+ (depending on your major version line)

  1. 1. Identify the currently installed Adobe Commerce/Magento version using the command: bin/magento --version
  2. 2. For Magento/OpenSource installations on 2.3.x: Upgrade to version 2.3.7-p4 or later (e.g., composer require magento/product-community-edition=2.3.7-p4 --no-update)
  3. 3. For Magento/OpenSource installations on 2.4.x: Upgrade to version 2.4.4 or later (e.g., composer require magento/product-community-edition=2.4.5 --no-update)
  4. 4. For Adobe Commerce (Cloud) installations: Upgrade to the corresponding patched versions (2.3.7-p4, 2.4.3-p3, or 2.4.5) as appropriate for your installation type
  5. 5. Run composer update to fetch the new packages: composer update
  6. 6. Clear the Magento cache: bin/magento cache:clean
  7. 7. Run the upgrade scripts if needed: bin/magento setup:upgrade
  8. 8. Re-index if necessary: bin/magento indexer:reindex
Caveat Review Adobe's release notes for 2.4.5 and 2.3.7-p4 for any breaking changes or known issues before upgrading, especially if using third-party extensions

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
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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