CVE-2024-34102
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.
- CVSS
- 9.8Criticalscored by the publisher (CNA)
- Exploited in the wild
- Yes, in CISA KEV since 17 Jul 2024CISA deadline for US federal agencies: 7 Aug 2024public exploit code
- EPSS
- > 99.9%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 13 Jun 2024analysed here 12 Nov 2026
Do first. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (CISA's required action for this KEV entry)
Summary
Triage
- Attack surface
- Server-side
- Exploitable
- At runtime
- Attack vector
- network
- Weakness
- CWE-611 XML External Entity (XXE)
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Adobe Adobe Commerce | <= 2.4.4-p8Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- adobe:commerce
- adobe:commerce_webhooks
- adobe:magento
Fix and mitigation
WAF and other mitigations
Can a WAF block it? Partly. Cloudflare publishes WAF a rule written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.
Cloudflare · 1 rule (Block) · since 6 Jan 2025
- Magento - XXE - CVE:CVE-2024-34102 · Cloudflare Specials
Also consider: patch · enable the vendor rule in block mode · disable DTDs in parser
Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 17 Jul 2024.
- CISA due date
- 7 Aug 2024, the remediation deadline for US federal agencies
- CISA required action
- Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- Public exploit code
- Yes: 2 Metasploit modules · 23 GitHub proofs of concept · 1 Nuclei template
- CISA SSVC
- exploitation active, automatable yes, technical impact totalAssessed by CISA 18 Jul 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Metasploit
- exploit/linux/http/magento_xxe_to_glibc_buf_overflowexploit, rank excellent
- auxiliary/gather/magento_xxe_cve_2024_34102auxiliary, rank normal
Nuclei
- Adobe Commerce & Magento - CosmicStingdetection template, critical
GitHub proofs of concept
- Chocapikk/CVE-2024-3410248 stars
- bigb0x/CVE-2024-3410231 stars
- th3gokul/CVE-2024-3410214 stars
- jakabakos/CVE-2024-34102-CosmicSting-XXE-in-Adobe-Commerce-and-Magento9 stars
and 19 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 13 Jun 2024Published
- 27 Jun 2024First public exploit or proof of concept14 days later
- 17 Jul 2024Added to CISA KEV (exploited in the wild)20 days later
- 18 Jul 2024CISA SSVC assessment: exploitation active1 day later
- 7 Aug 2024CISA remediation due date (US federal agencies)20 days later
- 21 Oct 2025CVE record last updated441 days (about 1 year) later
- 12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2024-34102 being exploited?
Yes. CVE-2024-34102 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-34102?
CVE-2024-34102 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-34102?
Yes. A fix has been recorded for CVE-2024-34102. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-34102 affect?
CVE-2024-34102 affects adobe:commerce, adobe:commerce_webhooks, adobe:magento. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
3 references in the CVE record, grouped by the tags the record gives them.
Advisories (1)
- helpx.adobe.com /security/products/magento/apsb24-40.html
Other links (2)
- vicarius.io /vsociety/posts/cosmicsting-critical-unauthenticated-xxe-vulnerability-in-adobe-
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-34102
Also tracked as GHSA-m8cj-3v68-3cxj (OSV).
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Metasploit Framework: exploit and scanner modules
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- OSV: advisory aliases and downstream package versions
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.