What is CVE-2024-34102?

CVE-2024-34102 is XXE can expose crypt key and other secrets granting full admin access. The supplied enrichment data classifies it as Injection mapped to CWE-611 XML External Entity Reference.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

74 public PoC repositories reported; 3 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, database audit logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2024-34102 using CVSS 9.8, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: MageCart (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVcriticalInjectionpublic exploit

CVE-2024-34102

CVE-2024-34102 — XXE can expose crypt key and other secrets granting full admin access

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2024-34102 in CISA KEV with required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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.

Published Jun 13, 2024Updated Jun 17, 2026Sources: NVD, Adobe (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Jul 17, 2024

EPSS

100%

top of FIRST's scoreset

Affects

Adobe

Adobe Commerce

CVSS base

9.8

critical

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Adobe Commerce to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Federal deadline Aug 7, 2024 — passed 770 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Adobe	Adobe Commerce	0 to <= 2.4.4-p8	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.8	CVSS 3.1	critical	3.9	5.9	Adobe (CNA)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-611 · Improper Restriction of XML External Entity Reference

Read Application Data
Read Files or Directories
Bypass Protection Mechanism
DoS: Resource Consumption (CPU)

Mitigation: Many XML parsers and validators can be configured to disable external entity expansion.::

Weakness & attack patterns

CWE-611XML External Entity Reference

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-221 · Data Serialization External Entities Blowup

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Jul 17, 2024

Federal deadline

Aug 7, 2024

passed 770 days ago

Ransomware use

Unknown

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 date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

3 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Adobe Commerce.
Monitor for scanner or exploit-pattern traffic after 74 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSdatabase audit logs

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

MageCart

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.8 (AV:N)
Jun 17, 2026 · NVD
Cve is exploited nmmorette/CVE-2024-34102
Feb 23, 2026 · SOCRadar CTI
2025
Cve is exploited bka/magento-cve-2024-34102-exploit-cosmicstring
Apr 7, 2025 · SOCRadar CTI
Bulletin released on Mitre.
Feb 13, 2025 · SOCRadar CTI
2024
Added to CISA KEV catalog
Jul 17, 2024 · CISA
Initial · CVE published
Jun 13, 2024 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

16×SVRS was changedFeb 12, 2025 – Mar 8, 2026 · SOCRadar CTI
5×ModifiedFeb 13, 2025 – Oct 23, 2025 · SOCRadar CTI
3×Github ReposApr 6, 2025 – Feb 13, 2026 · SOCRadar CTI
2×Tweets · 1 time tweeted.Sep 19, 2025 – Nov 21, 2025 · SOCRadar CTI

References

4 on the record

helpx.adobe.com/security/products/magento/apsb24-40.html
Vendor Advisory, NIST
www.vicarius.io/vsociety/posts/cosmicsting-critical-unauthenticated-xxe-vulnerability-in-adobe-commerce-and-magento-cve-2024-34102
Exploit, Technical Description, Third Party Advisory, NIST, GITHUB
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-34102
Third Party Advisory, US Government Resource
nvd.nist.gov/vuln/detail/CVE-2024-34102
Vendor Advisory

Coverage

8 stories from the feeds we poll

3 more reports on this CVEShowing 5 of 8 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Adobeevery CVE for this vendor
July 2024what else CISA listed
Injectionsame class
CWE-611other pages naming this weakness

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 record1

What should defenders know first?

CVE-2024-34102 is XXE can expose crypt key and other secrets granting full admin access, a critical vulnerability affecting Adobe Commerce from Adobe. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 74 public PoC repositories reported; 3 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.