# PhpSpreadsheet vulnerable to SSRF when reading and displaying a processed HTML document in the browser Advisory record · `GHSA-rx7m-68vc-ppxh` - **Identifiers:** `GHSA-rx7m-68vc-ppxh` · `CVE-2025-54370` · `PKSA-64jn-3d9t-gncx` - **State:** Confirmed - **Severity:** CVSS 8.7 High - **Critical:** No - **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html) - **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md) - **Published:** 25 Aug 2025 - **Updated:** 29 Aug 2025 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 25 Aug 2025, 14:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `phpoffice/phpspreadsheet` (Packagist): affected `<1.30.0 || >=2.0.0, <2.1.12 || >=2.2.0, <2.4.0 || >=3.0.0, <3.10.0 || >=4.0.0, <5.0.0`; fixed in `1.30.0`, `2.1.12`, `2.4.0`, `3.10.0`, `5.0.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > PhpSpreadsheet versions before 1.30.0, from 2.0.0 before 2.1.12, from 2.2.0 before 2.4.0, from 3.0.0 before 3.10.0, and from 4.0.0 before 5.0.0 are vulnerable to server-side request forgery when a string from a user is passed to the HTML reader and the processed document is displayed in a browser. An attacker who can supply that string can make the server send requests to addresses of their choosing. The source also mentions a possible phar deserialization opportunity but gives few details. Upgrade to 1.30.0, 2.1.12, 2.4.0, 3.10.0, or 5.0.0 depending on your release line. Written 3 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 - 8.7 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0082, the 57th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:26 UTC: First seen by agentprime - 31 Oct 2026, 14:26 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-rx7m-68vc-ppxh) ## Sources - [GitHub Advisory Database: GHSA-rx7m-68vc-ppxh](https://github.com/advisories/GHSA-rx7m-68vc-ppxh) - [OSV: GHSA-rx7m-68vc-ppxh](https://osv.dev/vulnerability/GHSA-rx7m-68vc-ppxh) - - - - - - - - - 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: .