dbcve.org
CommerceApplication · Adobe

CVE-2022-34259

MEDIUM · 5.3 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 →
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.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 a Security feature bypass. An attacker could leverage this vulnerability to impact the availability of a user's minor feature. 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

This is an Improper Access Control vulnerability in Adobe Commerce (Magento) that allows attackers to bypass security features and impact the availability of minor user features without requiring any user interaction. The vulnerability affects multiple versions of Adobe Commerce across the 2.3.7 and 2.4.x release lines.

MitigationApply the vendor-supplied security patch for CVE-2022-34259 to affected Adobe Commerce installations. Upgrade to a patched version (2.4.3-p3 or later for the 2.4.3 line, 2.3.7-p4 or later for the 2.3.7 line, or 2.4.4-p1 or later for the 2.4.4 line).

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

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

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
    Locate the composer.json file in the Magento root directory and check the 'version' field, or log into the Admin panel and navigate to System > Settings > About Adobe Commerce (or System > Tools > Section 'General' > Version)
    Affected if The version shown is any of the following: 2.3.0 through 2.3.7 (any patch), 2.4.0 through 2.4.3 (any patch), or exactly 2.4.4
  2. Check for applied security patches
    Search the composer.json file or composer.lock file for entries related to security patch AC-2xxx (the specific patch for CVE-2022-34259), or check the app/etc/patches directory for applied patch files
    Affected if No patch file for CVE-2022-34259 is found in the applied patches list or composer entries
  3. Verify the exact patch version if using 2.3.7
    For installations reporting version 2.3.7, confirm whether the patch level is below p4 by checking composer.json version string (e.g., 2.3.7-p1, 2.3.7-p2, 2.3.7-p3 are vulnerable; 2.3.7-p4 and above are not)
    Affected if The version shows 2.3.7 without the -p4 suffix or higher patch level
  4. Verify the exact patch version if using 2.4.3
    For installations reporting version 2.4.3, confirm whether the patch level is below p3 by checking composer.json version string
    Affected if The version shows 2.4.3 without the -p3 suffix or higher patch level
  5. Verify the exact patch version if using 2.4.4
    For installations reporting version 2.4.4, confirm whether the patch level is below p1 by checking composer.json version string
    Affected if The version shows 2.4.4 without the -p1 suffix or higher patch level

Your environment is affected if the installed Adobe Commerce or Magento version falls within 2.3.0 to 2.3.7, 2.4.0 to 2.4.3, or exactly 2.4.4, and no corresponding security patch has been applied.

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.

From vendor data
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 for CVE-2022-34259 to affected Adobe Commerce installations. Upgrade to a patched version (2.4.3-p3 or later for the 2.4.3 line, 2.3.7-p4 or later for the 2.3.7 line, or 2.4.4-p1 or later for the 2.4.4 line).

Fix this in Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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