dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 1 Mar 2022.
CommerceApplication · Adobe

CVE-2022-24086

CRITICAL · 9.8 CVSS v3.1 Published 2022-02-16
Fix available
A fix is available. Upgrade to 2.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click Patch available

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-p1 (and earlier) and 2.3.7-p2 (and earlier) are affected by an improper input validation vulnerability during the checkout process. Exploitation of this issue does not require user interaction and could result in arbitrary code execution.

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 input validation vulnerability in the checkout process that allows unauthenticated attackers to inject and execute arbitrary code on the server. The lack of input sanitization during checkout enables remote code execution without any user interaction.

MitigationApply the official Adobe security patches or upgrade to the patched versions (2.4.3-p2 or later for the 2.4.x branch, 2.3.7-p3 or later for the 2.3.x branch) immediately as this vulnerability has known active exploitation.

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.3, <= 2.3.6>= 2.4.0, <= 2.4.2= 2.3.7= 2.4.3
MagentoCMS
Affected:< 2.3.0> 2.3.3, <= 2.3.6>= 2.4.0, <= 2.4.2= 2.3.7= 2.4.3

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check installed Adobe Commerce or Magento version
    Run 'bin/magento --version' from the installation root directory, or inspect the composer.json file for the 'version' field, or look at the admin panel footer which displays the version number
    Affected if The installed version is < 2.3.0, or between 2.3.3 and 2.3.6 inclusive, or exactly 2.3.7, or between 2.4.0 and 2.4.2 inclusive, or exactly 2.4.3 (or if the version cannot be determined but is known to be from before February 2022 without patches applied)
  2. Confirm the checkout module is enabled
    Run 'bin/magento module:status Magento_Checkout' or check the admin panel under Stores > Configuration > Advanced > Advanced to verify the checkout module is not disabled
    Affected if The checkout module is enabled (this is the default configuration for most Adobe Commerce/Magento installations)
  3. Check if the security patch MDVA-43395 or MDVA-43453 has been applied
    Search the codebase for the specific code changes from the patch, particularly in the file vendor/magento/module-checkout/Controller/Index/Index.php or related checkout controllers, looking for the input validation fixes that address the CVE
    Affected if The patch code changes are NOT present in the checkout controller files, indicating the vulnerability remains unmitigated

A user is affected if their Adobe Commerce or Magento installation version falls within the vulnerable ranges AND the checkout module is enabled AND the official security patch has not 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.

dbcve · scoped
Upgrade available Upgrade to 2.3.0 or later
Fixed in 2.3.0
Vendor patch helpx.adobe.com →
Interim mitigation

Apply the official Adobe security patches or upgrade to the patched versions (2.4.3-p2 or later for the 2.4.x branch, 2.3.7-p3 or later for the 2.3.x branch) immediately as this vulnerability has known active exploitation.

Recommended fix High confidence

Adobe Commerce 2.4.3-p2+ (or 2.4.4+) / 2.3.7-p3+

  1. Determine current Adobe Commerce or Magento version by checking the admin panel or composer.json
  2. For Adobe Commerce/Magento 2.4.x series: Upgrade to version 2.4.3-p2 or later (preferably 2.4.4 or newer)
  3. For Adobe Commerce/Magento 2.3.x series: Upgrade to version 2.3.7-p3 or later
  4. After upgrade, verify the installation using bin/magento --version command
  5. Clear the cache using bin/magento cache:flush
  6. Test the checkout process to ensure functionality
Caveat Security patch-only upgrades typically have minimal breaking changes; review release notes for any specific notes

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

Fix this in Commerce Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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