# XXE in PHPSpreadsheet's XLSX reader Advisory record · `GHSA-7cc9-j4mv-vcjp` - **Identifiers:** `GHSA-7cc9-j4mv-vcjp` · `CVE-2024-48917` · `PKSA-gst3-cdk3-bpqt` · `PKSA-j2jw-2hjb-39hn` - **State:** Confirmed - **Severity:** CVSS 7.5 High - **Critical:** No - **Weakness (CWE):** [CWE-611](https://cwe.mitre.org/data/definitions/611.html) - **Tags:** [XML external entities (XXE)](https://agentprime.io/advisories/tag/xxe.md) - **Published:** 18 Nov 2024 - **Updated:** 6 Mar 2025 - **Reviewed by a person:** No 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. ## Affected packages - `phpoffice/phpspreadsheet` (Packagist): affected `<1.29.4 || >=2.0.0, <2.1.3 || >=2.2.0, <2.3.2 || >=3.3.0, <3.4.0`; fixed in `1.29.4`, `2.1.3`, `2.3.2`, `3.4.0` - `phpoffice/phpexcel` (Packagist): affected `<=1.8.2`; no fixed version yet ## 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 - 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from 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 - 31 Oct 2026, 14:27 UTC: First seen by agentprime - 31 Oct 2026, 14:27 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7cc9-j4mv-vcjp) ## Sources - [GitHub Advisory Database: GHSA-7cc9-j4mv-vcjp](https://github.com/advisories/GHSA-7cc9-j4mv-vcjp) - [OSV: GHSA-7cc9-j4mv-vcjp](https://osv.dev/vulnerability/GHSA-7cc9-j4mv-vcjp) - - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .