CVE-2024-34102

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Adobe Commerce and Magento Open Source. For every flaw being used in attacks, see Exploited flaws; for Adobe’s, see Adobe flaws being used in attacks.

CVE-2024-34102 is a security flaw in Adobe Commerce and Magento Open Source, software for running online shops. Attackers can run their own code on Adobe Commerce and Magento Open Source. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 17 Jul 2024.[1]

Adobe Commerce and Magento Open Source is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Adobe has published a fix or advice.

Description

CISA calls it an improper restriction of XML external entity reference (XXE) in Adobe Commerce and Magento Open Source. In its words: “Adobe Commerce and Magento Open Source contain an improper restriction of XML external entity reference (XXE) vulnerability that allows for remote code execution.”[1]

The CVE record adds: “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.”[2]

The underlying weakness is XML external entity (CWE-611), in MITRE’s list of common software weaknesses.

It scores 9.8 out of 10 on the Common Vulnerability Scoring System, which rates it critical, scored by the organisation that published the CVE using CVSS 3.1.[2]

Affected versions

NVD’s record doesn’t list version ranges for it; Adobe’s advisory has them[3]. CISA names the product as Adobe Commerce and Magento Open Source.

Most families won’t have Adobe Commerce and Magento Open Source; it’s for whoever looks after IT at work.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 17 Jul 2024, 34 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 7 Aug 2024 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at over 99%. That’s in the top 1% of the flaws it scores.[4]

CISA assesses it as automatable: attackers can run it against many targets at once.

CISA doesn’t say who was attacked, or how.

Fix

Adobe has published a fix or advice.[3] CISA’s required action: “Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.”[1]

  1. Check whether you use it.Adobe Commerce and Magento Open Source is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
  2. Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 7 Aug 2024 to fix it.
  3. If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.

You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 9.8.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at over 99%.[4]

See also

Other Adobe Commerce and Magento Open Source flaws

Other Adobe flaws

  • CVE-2026-48356, Adobe Commerce and Magento: unrestricted upload of file with dangerous type ·
  • CVE-2026-71362, Adobe Commerce and Magento: incorrect authorization ·
  • CVE-2026-75650, Adobe Commerce and Magento: improper neutralization of special elements used in a template engine ·
  • CVE-2026-48282, Adobe ColdFusion: path traversal ·
  • CVE-2009-3459, Adobe Acrobat and Reader: heap-based buffer overflow ·

Other XML external entity flaws

  • CVE-2025-58360, OSGeo GeoServer: improper restriction of XML external entity reference ·
  • CVE-2025-2776, SysAid On-Prem: on-prem improper restriction of XML external entity reference ·
  • CVE-2025-2775, SysAid On-Prem: on-prem improper restriction of XML external entity reference ·
  • CVE-2023-45727, North Grid Proself: improper restriction of XML external entity (XXE) reference ·
  • CVE-2019-9670, Synacor Zimbra Collaboration Suite (ZCS): improper restriction of XML external entity reference ·

Added the same day

  • CVE-2024-28995, SolarWinds Serv-U: path traversal ·
  • CVE-2022-22948, VMware vCenter Server: incorrect default file permissions ·

Every Adobe flaw on CISA’s list · Everything added in July 2024

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Adobe Commerce and Magento Open Source Improper Restriction of XML External Entity Reference (XXE) Vulnerability”. Known Exploited Vulnerabilities Catalog, added 17 Jul 2024.
  2. ^ National Institute of Standards and Technology. “CVE-2024-34102 Detail”. National Vulnerability Database, published 13 Jun 2024.
  3. ^ Adobe. Advisories and fixes: helpx.adobe.com.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 1.000, percentile 100.0, 31 Oct 2026.
  5. CVE Program. “CVE-2024-34102”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.