NVD / CVE Program· CNA adobe

CVE-2022-24086: Adobe Commerce checkout improper input validation leads to remote code execution

Noroxi assessment

Priority: Now (action score 99/100)

CISA has confirmed exploitation in the wild (Feb 15, 2022). Remediation deadline for US federal agencies: Mar 1, 2022.
A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
Probability of exploitation in the next 30 days: 99.1% (FIRST EPSS); higher than 99.9% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: magento/community-edition (Packagist) 2.3.7-p3, 2.4.3-p2.
Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Patch today or shut off access. Upgrade to magento/community-edition (Packagist) 2.3.7-p3, 2.4.3-p2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS

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.

CriticalCVSS 9.8 · v3.1KEVWeaponized Fix available

pre-auth RCE

Published: Feb 16, 2022
Updated: Jun 17, 2026
EPSS: 99.1% · 99th percentile
CWE: CWE-20

Report tools

JSON

Action score

Now

Patch today or shut off access.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 30 / 30 · Listed
EPSS: 30 / 30 · 99.1%

CISA SSVC decision

Exploitation: active
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · adobe: 9.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on Feb 15, 2022. That signals real attacks, not theory.

Remediation deadline for US federal agencies: Mar 1, 2022.

Get told when this record changes

In CISA KEV: exploitation in the wild confirmed
Weaponized exploit exists
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
adobe	commerce	cpe:2.3:a:adobe:commerce
adobe	magento	cpe:2.3:a:adobe:magento

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

adobe commercebefore 2.3.0
adobe commerce2.3.3 and later · up to 2.3.6 inclusive
adobe commerce2.4.0 and later · up to 2.4.2 inclusive
adobe commerce2.3.7
adobe commerce2.4.3
adobe magentobefore 2.3.0
adobe magentoafter 2.3.3 · up to 2.3.6 inclusive
adobe magento2.4.0 and later · up to 2.4.2 inclusive
adobe magento2.3.7
adobe magento2.4.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (adobe). Independent of NVD's CPE analysis and usually ahead of it.

Adobe Magento Commerce
- unspecified and later · up to and including 2.4.3-p1affected
- unspecified and later · up to and including 2.3.7-p2affected
- unspecified and later · up to and including Noneaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Packagist	magento/community-edition	from 2.3.3-p1 · before 2.3.7-p3	2.3.7-p3
Packagist	magento/community-edition	from 2.4.0 · before 2.4.3-p2	2.4.3-p2

Same product

adobe: all records

Other highest-scoring records for the same primary product.

CVE-2024-34102XXE can expose crypt key and other secrets granting full admin accessKEV
99Now
CVE-2025-54236Adobe Commerce | Improper Input Validation (CWE-20)KEV
95Now
CVE-2026-71362Adobe Commerce | Incorrect Authorization (CWE-863)KEV
93Now

Published before and after this one in the same product

← EarlierCVE-2021-39864Oct 15, 2021 · Adobe Commerce Cross-Site Request Forgery (CSRF) Could Lead To Unauthorized Cart Addition
26Monitor
Later →CVE-2022-34253Aug 16, 2022 · Adobe Commerce XML Injection Arbitrary code execution
30Monitor
Later →CVE-2022-34254Aug 16, 2022 · Adobe Commerce Improper Limitation of a Pathname to a Restricted Directory Arbitrary code execution
36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Packagist:magento/community-edition	2.3.7-p3	Package registry (OSV)
Packagist:magento/community-edition	2.4.3-p2	Package registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

Nuclei detection template ×1
Proof-of-concept repository on GitHub ×9

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Nuclei detection template	Nuclei template CVE-2022-24086	—
Proof-of-concept repository on GitHub	stars:35	2022-02-20
Proof-of-concept repository on GitHub	stars:0	2022-02-28
Proof-of-concept repository on GitHub	stars:0	2022-03-15
Proof-of-concept repository on GitHub	stars:6	2022-05-19
Proof-of-concept repository on GitHub	stars:2	2022-06-12
Proof-of-concept repository on GitHub	stars:2	2022-10-01
Proof-of-concept repository on GitHub	stars:6	2022-12-20
Proof-of-concept repository on GitHub	stars:0	2023-09-03
Proof-of-concept repository on GitHub	stars:0	2024-11-25

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

CISA KEVFeb 15, 2022-2 d
PublishedFeb 16, 2022
First PoCFeb 20, 2022+3 d
TodayNov 8, 2026+1726 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).