CVE-2026-59931 json
PhpSpreadsheet: SSRF bypass via HTTP redirect in WEBSERVICE() domain whitelist
published 2026-07-23 3 mo ago modified 2026-10-23 16 d ago also EUVD-2026-49929 , GHSA-6hq5-7373-42rg
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
PhpSpreadsheet is a pure PHP library for reading and writing spreadsheet files. In versions 4.0.0 through 5.8.0, 3.3.0 through 3.10.6, 2.2.0 through 2.4.6, 2.0.0 through 2.1.17, and all releases up to and including 1.30.5, the WEBSERVICE() domain whitelist can be bypassed via an HTTP redirect (SSRF). In Calculation/Web/Service.php, the webService() method validates a URL's host against the whitelist set via Spreadsheet::setDomainWhiteList(), then fetches content with file_get_contents($url, false, $ctx); because PHP's HTTP stream wrapper follows 301/302 redirects automatically (up to 20 hops) and the redirect target is never re-validated, an attacker who can trigger a redirect from a whitelisted domain can reach arbitrary URLs, including internal addresses. An attacker able to upload XLSX files to an application that uses setDomainWhiteList() and getCalculatedValue() can achieve a full-read SSRF, returning up to 32,767 bytes of the response body as a cell's calculated value, which enables exfiltration of cloud metadata (AWS/GCP/Azure credentials via http://169.254.169.254/), access to internal-only services, and internal port scanning (the port is not validated). This issue has been fixed in versions 5.8.1, 3.10.7, 2.4.7, 2.1.18, and 1.30.6.
Patch / fix
- packagist phpoffice/phpspreadsheet 1.30.6, 2.1.18, 2.4.7, 3.10.7, 5.8.1
- phpoffice phpspreadsheet 1.30.6, 2.1.18, 2.4.7, 3.10.7, 5.8.1
- phpspreadsheet_project phpspreadsheet 1.30.6, 2.1.18, 2.4.7, 3.10.7, 5.8.1
- github.com/PHPOffice/PhpSpreadsheet@7ef7b25 commit
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/1.30.6 release
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/2.1.18 release
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/2.4.7 release
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/3.10.7 release
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/5.8.1 release
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/PHPOffice/PhpSpreadsheet/security/advisories/GHSA-6hq5-7373-42rg referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
| GitHub | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | phpoffice/phpspreadsheet | >=4.0.0, <5.8.1 >=3.3.0, <3.10.7 >=2.2.0, <2.4.7 >=2.0.0, <2.1.18 <1.30.6 |
5.8.1 3.10.7 2.4.7 2.1.18 1.30.6 |
Affected products
- PHPOffice PhpSpreadsheet
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/PHPOffice/PhpSpreadsheet/commit/7ef7b25e8548a6ded79dac74e2e2c7acdac38d8d
web
-
github.com
/PHPOffice/PhpSpreadsheet/security/advisories/GHSA-6hq5-7373-42rg
exploit, web
-
github.com
/PHPOffice/PhpSpreadsheet/releases/tag/1.30.6
web
-
github.com
/PHPOffice/PhpSpreadsheet/releases/tag/2.1.18
web
-
github.com
/PHPOffice/PhpSpreadsheet/releases/tag/2.4.7
web
-
github.com
/PHPOffice/PhpSpreadsheet/releases/tag/3.10.7
web
-
github.com
/PHPOffice/PhpSpreadsheet/releases/tag/5.8.1
web
-
github.com
/PHPOffice/PhpSpreadsheet
package
Sources
- CVE List CVE-2026-59931
- GitHub Advisory GHSA-6hq5-7373-42rg
- NVD CVE-2026-59931
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.