CVE-2026-59931: PHPOffice PhpSpreadsheet · Server-Side Request Forgery (SSRF)
Affects PHPOffice PhpSpreadsheetSource CVE Database V5
Not known to be exploited · CVSS 7.7 High · fixed in 5.8.1 : patch PHPOffice PhpSpreadsheet soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.8.1, 3.10.7, 2.4.7 +2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PHPOfficePhpSpreadsheet | Affected
| Fixed in
|
| PHPOfficePhpSpreadsheet | Affected
| Fixed in
|
| PHPOfficePhpSpreadsheet | Affected
| Fixed in
|
| PHPOfficePhpSpreadsheet | Affected
| Fixed in
|
| PHPOfficePhpSpreadsheet | Affected
| Fixed in
|
AI-suggested
A fix is available in PhpSpreadsheet versions 5.8.1, 3.10.7, 2.4.7, 2.1.18, and 1.30.6. Users should upgrade to these or later versions to remediate the vulnerability. Since this is a cloud service, the vendor manages remediation for the cloud-hosted service; users should verify with the vendor that their environment is updated accordingly. Until patched, avoid processing untrusted XLSX files that use the WEBSERVICE() function with domain whitelisting.
Description
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.
References
- github.com/PHPOffice/PhpSpreadsheet/security/advisories/GHSA-6hq5-7373-42rg (opens in a new tab)
- github.com/PHPOffice/PhpSpreadsheet/commit/7ef7b25e8548a6ded79dac74e2e2c7acdac38d8d (opens in a new tab)
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/1.30.6 (opens in a new tab)
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/2.1.18 (opens in a new tab)
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/2.4.7 (opens in a new tab)
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/3.10.7 (opens in a new tab)
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/5.8.1 (opens in a new tab)