How severe is CVE-2025-22131?

No CVSS score has been assigned to CVE-2025-22131 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-22131?

CVE-2025-22131 affects the following packages: phpoffice/phpspreadsheet (Packagist), phpoffice/phpspreadsheet (Packagist), phpoffice/phpspreadsheet (Packagist), phpoffice/phpspreadsheet (Packagist), phpoffice/phpexcel (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2025-22131?

Update phpoffice/phpspreadsheet to 3.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-22131 is resolved across your whole dependency graph.

How do I detect CVE-2025-22131 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpoffice/phpspreadsheet. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2025-22131 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-22131?

O3 pinpoints whether CVE-2025-22131 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2025-22131 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2025-22131, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-22131?

CVE-2025-22131 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 29th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2025-22131 published, and has it been updated?

CVE-2025-22131 was published on January 20, 2025 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

CVE-2025-22131

Cross-Site Scripting (XSS) vulnerability in generateNavigation() function

Also known asGHSA-79xx-vf93-p7cx

Published

Jan 20, 2025

Updated

Apr 10, 2026

Affected

5 pkgs

Patched

4 / 5

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk29th percentile-0.34%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

5 pkgs affected

🐘phpoffice/phpspreadsheet🐘phpoffice/phpspreadsheet🐘phpoffice/phpspreadsheet🐘phpoffice/phpspreadsheet🐘phpoffice/phpexcel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

PhpSpreadsheet is a PHP library for reading and writing spreadsheet files. Cross-Site Scripting (XSS) vulnerability in the code which translates the XLSX file into a HTML representation and displays it in the response.

Affected Packages

5 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`phpoffice/phpspreadsheet`	≥ 3.0.0&&< 3.8.0	3.8.0
🐘Packagist	`phpoffice/phpspreadsheet`	all versions	1.29.8
🐘Packagist	`phpoffice/phpspreadsheet`	≥ 2.0.0&&< 2.1.7	2.1.7
🐘Packagist	`phpoffice/phpspreadsheet`	≥ 2.2.0&&< 2.3.6	2.3.6
🐘Packagist	`phpoffice/phpexcel`	all versions	No fix

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

s0ck37/CVE-2025-22131-POC

POC for the vuln CVE-2025-22131

⭐ 3🍴 1Feb 2026

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpoffice/phpspreadsheet. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update phpoffice/phpspreadsheet to 3.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-22131 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-22131 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-22131. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-22131 in your dependencies?

O3 detects CVE-2025-22131 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works