CVE-2024-34102 — Adobe Commerce and Magento Open Source Improper Restriction of XML External Entity Reference (XXE) Vulnerability
Adobe Commerce versions 2.4.7, 2.4.6-p5, 2.4.5-p7, 2.4.4-p8 and earlier are affected by an Improper Restriction of XML External Entity Reference ('XXE') vulnerability that could result in arbitrary code execution. An attacker could exploit this vulnerability by sending a crafted XML document that references external entities. Exploitation of this issue does not require user interaction.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (nuclei, metasploit, github)+20
- EPSS 100% (30-day exploitation probability)+15
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Composer Magento/community-edition: fixed in version 2.4.6-p6 — github.com (GitHub Security Advisories)
- Composer Magento/community-edition: fixed in version 2.4.5-p8 — github.com (GitHub Security Advisories)
- Composer Magento/community-edition: fixed in version 2.4.4-p9 — github.com (GitHub Security Advisories)
CISA required action CISA
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
US federal deadline: Aug 7, 2024 — passed 799 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Adobe Commerce, Adobe Commerce Webhooks, Adobe Magento…).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Adobe | Commerce |
version 2.4.5-p7version 2.4.4-p6version 2.4.4-p8version 2.4.5version 2.4.5-p1version 2.4.5-p2version 2.4.5-p3version 2.4.5-p4 and 25 moreversion 2.4.5-p5version 2.4.2-ext-1version 2.4.6version 2.4.6-p1version 2.4.6-p2version 2.4.6-p3version 2.4.6-p5version 2.4.7version 2.4.4-p4version 2.4.4-p5version 2.4.2version 2.4.2-ext-2version 2.4.2-ext-3version 2.4.2-ext-4version 2.4.2-ext-7version 2.4.3version 2.4.3-ext-1version 2.4.3-ext-3version 2.4.3-ext-4version 2.4.3-ext-7version 2.4.4version 2.4.4-p1version 2.4.4-p2version 2.4.4-p3version 2.4.3-ext-2 |
Vulnerable | NIST National Vulnerability Database |
| Adobe | Commerce | ≤ 2.4.4-p8 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Adobe | Commerce Webhooks | ≥ 1.2.0 and < 1.5.0 | Vulnerable | NIST National Vulnerability Database |
| Adobe | Magento |
version 2.4.5-p5version 2.4.5-p6version 2.4.5-p7version 2.4.6version 2.4.4-p8version 2.4.6-p1version 2.4.6-p2version 2.4.6-p3 and 17 moreversion 2.4.6-p4version 2.4.6-p5version 2.4.7version 2.4.7-b1version 2.4.5-p3version 2.4.4version 2.4.4-p1version 2.4.4-p2version 2.4.4-p3version 2.4.4-p4version 2.4.4-p5version 2.4.4-p6version 2.4.4-p7version 2.4.5version 2.4.5-p1version 2.4.5-p2version 2.4.5-p4 |
Vulnerable | NIST National Vulnerability Database |
| Composer | Magento/community-edition | version 2.4.4≥ 2.4.6-p1 and < 2.4.6-p6≥ 2.4.5-p1 and < 2.4.5-p8< 2.4.4-p9version 2.4.5version 2.4.6version 2.4.7 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | psirt@adobe.com via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 9.8 | CVSS 3.1 | Critical | — | — | adobe via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: psirt@adobe.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- Magento XXE Unserialize Arbitrary File Read normal Jun 11, 2024
- CosmicSting: Magento Arbitrary File Read (CVE-2024-34102) + PHP Buffer Overflow in the iconv() function of glibc (CVE-2024-2961) excellent Jul 26, 2024
- CosmicSting (CVE-2024-34102) ★ 48 Jun 28, 2024
- POC for CVE-2024-34102. A pre-authentication XML entity injection issue in Magento / Adobe Commerce. ★ 31 Jun 27, 2024
- CVE-2024-34102: Unauthenticated Magento XXE ★ 14 Jun 27, 2024
- CosmicSting: critical unauthenticated XXE vulnerability in Adobe Commerce and Magento (CVE-2024-34102) ★ 9 Jul 1, 2024
- Exploitation CVE-2024-34102 ★ 5 Jul 13, 2024
- Adobe Commerce XXE exploit ★ 5 Aug 13, 2024
- POC for CVE-2024-34102 : Unauthenticated Magento XXE and bypassing WAF , You will get http connection on ur webhook ★ 3 Jun 28, 2024
- CVE-2024-34102 (Magento XXE) ★ 2 Jun 30, 2024
- Phantom-IN/CVE-2024-34102 ★ 1 Jul 14, 2024
- An alternative solution(as a Magento 2 extension) to fix the XXE vulnerability CVE-2024-34102(aka Cosmic Sting). If you cannot upgrade Magento or cannot apply the official patch, try this one. ★ 1 Aug 8, 2024
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 99.99%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
- Hunt retroactively in logs from before Jul 17, 2024 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · composer/magento/community-edition
- Affected products added · adobe/adobe commerce
- SSVC assessment updated
- Record published
- Affected products added · adobe/commerce, adobe/commerce webhooks, adobe/magento
- CVSS changed · 9.8
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- 2024
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
10 on the record
- helpx.adobe.com/security/products/magento/apsb24-40.html
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- github.com/magento/magento2/commit/c5c538810b87449886f4669cb8abbe8e5593c83c
- github.com/magento/magento2/commit/30877fce83b793f71421c47347885cf076e81799
- github.com/FriendsOfPHP/security-advisories/blob/master/magento/product-communit
- www.vicarius.io/vsociety/posts/cosmicsting-critical-unauthenticated-xxe-vulnerability
- github.com/advisories/GHSA-m8cj-3v68-3cxj
- github.com/magento/magento2/commit/a3c6d6e5e95e63031e4df26cfcf76feace7549c2
- github.com/magento/magento2/commit/d10435b11ada4e502dca7539f8fd31d059d3c482
- nvd.nist.gov/vuln/detail/CVE-2024-34102
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-95631 Adobe Commerce | Improper Input Validation (CWE-20) 2d
- Medium CVE-2026-95630 Adobe Commerce | Improper Input Validation (CWE-20) 2d
- Critical CVE-2026-92909 Adobe Commerce | Incorrect Authorization (CWE-863) 2d
- Critical CVE-2026-91013 Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79) 2d
- High CVE-2026-92908 Adobe Commerce | Incorrect Authorization (CWE-863) 2d
- Critical CVE-2026-92464 Adobe Commerce | Improper Input Validation (CWE-20) 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2024-34102 is "Adobe Commerce and Magento Open Source Improper Restriction of XML External Entity Reference (XXE) Vulnerability", rated Critical. It affects Commerce (Adobe); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 99.99% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.