CVE Tools
Track your stack

CVE-2024-47873

PhpSpreadsheet XmlScanner bypass leads to XXE

No known exploitation. EPSS puts it in the 54th percentile. Fixed in 1.29.4.

CVSS 3.17.5HighEPSS percentile54th0.7% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix1.29.4Upgrade to this build

Published Updated Sources: CVE.org, NVD, GitHub

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • PHPOffice PhpSpreadsheetAffected: < 1.29.4Upgrade to: not statedAffected: >= 2.0.0, < 2.1.3Upgrade to: not statedAffected: >= 2.2.0, < 2.3.2Upgrade to: not statedAffected: >= 3.3.0, < 3.4.0Upgrade to: not statedStated by: CVE record
  • Packagist phpoffice/phpspreadsheetAffected: < 1.29.4Upgrade to: 1.29.4Stated by: GitHub advisory
  • Packagist phpoffice/phpexcelAffected: ≤ 1.8.2Upgrade to: after 1.8.2Stated by: GitHub advisory

Versions as the sources state them. Full version matrix after sign-in

Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

PhpSpreadsheet is a PHP library for reading and writing spreadsheet files. The XmlScanner class has a scan method which should prevent XXE attacks. However, prior to versions 1.9.4, 2.1.3, 2.3.2, and 3.4.0, the regexes used in the `scan` method and the findCharSet method can be bypassed by using UCS-4 and encoding guessing. An attacker can bypass the sanitizer and achieve an XML external entity attack. Versions 1.9.4, 2.1.3, 2.3.2, and 3.4.0 fix the issue.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS54th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.7% chance of exploitation activity in the next 30 days, which ranks it in the 54th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 109 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Publishedweakness classified, att&ck mapped

Affected products

And 1 more affected product. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

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

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 3 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Phpoffice/phpspreadsheet, not every advisory.