Advisory record · GHSA-7cc9-j4mv-vcjp

XXE in PHPSpreadsheet's XLSX reader

CVSS 7.5 HighEPSS 0.0073 · 54th percentile

Published by the GitHub Advisory Database at 18 Nov 2024, 20:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
phpoffice/phpspreadsheetPackagist<1.29.4 || >=2.0.0, <2.1.3 || >=2.2.0, <2.3.2 || >=3.3.0, <3.4.01.29.4, 2.1.3, 2.3.2, 3.4.0
phpoffice/phpexcelPackagist<=1.8.2No fixed version yet
Identifiers
GHSA-7cc9-j4mv-vcjp · CVE-2024-48917 · PKSA-gst3-cdk3-bpqt · PKSA-j2jw-2hjb-39hn
Weakness (CWE)
CWE-611
Published
18 Nov 2024
Updated
6 Mar 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

PhpSpreadsheet versions below 1.29.4, from 2.0.0 below 2.1.3, from 2.2.0 below 2.3.2, and from 3.3.0 below 3.4.0 are vulnerable to XML external entity (XXE) attacks in the XLSX reader, because a crafted UTF-7 encoding declaration bypasses the XML scanner's encoding check. An attacker who can get a user to open a malicious XLSX file could trigger outbound requests and access local files. Upgrade to 1.29.4, 2.1.3, 2.3.2, or 3.4.0 depending on your branch. The phpoffice/phpexcel package (versions 1.8.2 and below) is also listed as affected, with no fixed version listed.

Written 4 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0073, the 54th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:27 UTC First seen by agentprime
  2. 31 Oct 2026, 14:27 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.