← Back
CVE-2026-59931
high
CVSS 7.7
SSRF (Server-Side Request Forgery) in phpoffice/phpspreadsheet (CVE-2026-59931)
Summary
SSRF in phpoffice/phpspreadsheet (CVE-2026-59931). Confidential information can be exposed externally. Exploitable via ``example.com``. Mitigation: upgrade to `1.30.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-59931** has been found in phpoffice/phpspreadsheet.
Attackers can target a specific entry point like ``example.com`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade phpoffice/phpspreadsheet to **1.30.6** or later.
If unsure, ask your IT team or search "phpoffice/phpspreadsheet CVE-2026-59931" on the vendor's site.
CVE-2026-59931 (phpoffice/phpspreadsheet) — CWE-918 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `example.com` / `file_get_contents`
Patched: `1.30.6` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**SSRF** (CWE-918) exists in phpoffice/phpspreadsheet. Attackers reach the vulnerable code path via ``example.com`` without authentication.
📍 Affected scope
phpoffice/phpspreadsheet — . Attack surface: `example.com` / `file_get_contents`.
🔥 Severity
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.30.6**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'phpoffice/phpspreadsheet' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'phpoffice/phpspreadsheet' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `phpoffice/phpspreadsheet` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade phpoffice/phpspreadsheet to 1.30.6ステージング環境で 1.30.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
phpoffice/phpspreadsheet
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.30.6"}]}]