CVE-2026-40296·PHP vulnerability
PhpSpreadsheet is a pure PHP library for reading and writing spreadsheet files. The HTML writer skips htmlspecialchars escaping when a cell's formatted value differs from the original value. When a cell has a custom number format containing the text placeholder @ along with any additional literal characters (for example ". @", "@ ", or "x@"), the formatter replaces @ with the cell value and adds the extra characters, causing the formatted value to differ from the original and bypassing HTML escaping entirely. An attacker who can control the cell value and number format of an uploaded spreadsheet that is later converted to HTML and displayed to other users can achieve stored cross-site scripting. This issue is fixed in versions 5.7.0, 3.10.5, 2.4.5, 2.1.16, and 1.30.4.
- Severity
- medium
- Software
- PHP
- Fixed in
- 5.7.0
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at <0.1% — higher than 8% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
From: 4.0.0
Until: 5.7.0
Fixed in: 5.7.0
How to fix this CVE
Update PhpSpreadsheet to version 5.7.0 or later to patch the HTML escaping bypass in the number formatter. If you maintain applications that convert user-uploaded spreadsheets to HTML, prioritize this update immediately, as attackers can inject malicious scripts through specially crafted cell formats. Verify the update is applied before accepting new spreadsheet uploads.
sudo dnf update phpDefensia detects this vulnerability
WAF mitigation (if patching is not yet possible)
Add this rule to your WAF to block exploitation attempts while you schedule the patch.
Implement input validation to reject spreadsheet uploads containing cell number formats with @ placeholder characters followed by arbitrary literals (regex: `@[^@]+`). Additionally, enforce Content-Security-Policy headers with `script-src 'self'` on pages displaying converted spreadsheet HTML to mitigate stored XSS impact.How to check if you are affected
- Run `php -v` to check the installed PHP version and verify PhpSpreadsheet library version via `composer show phpoffice/phpspreadsheet` if Composer is used
- Check if your application processes spreadsheet uploads and converts them to HTML output by reviewing upload handlers and HTML conversion code paths
- Search application logs and web server access logs for requests containing uploaded spreadsheet files followed by HTML rendering, specifically for patterns with custom number formats using @ placeholder
- After updating to 5.7.0 or later, run `composer update phpoffice/phpspreadsheet` and verify the updated version with `composer show phpoffice/phpspreadsheet | grep Version`
FAQ
What is CVE-2026-40296?
CVE-2026-40296 is a stored cross-site scripting vulnerability in PhpSpreadsheet's HTML writer that occurs when cells use custom number formats with the @ placeholder combined with additional characters. The formatter bypasses HTML escaping by creating a formatted value that differs from the original, allowing attackers to inject malicious scripts through spreadsheet uploads.
Is CVE-2026-40296 being actively exploited?
No, CVE-2026-40296 is not listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits are currently available, though the vulnerability is straightforward to exploit once understanding the number format bypass mechanism.
What versions of PHP are affected by CVE-2026-40296?
PhpSpreadsheet versions 4.0.0 through 5.7.0 are affected. Earlier branches have separate patched versions: 3.10.5, 2.4.5, 2.1.16, and 1.30.4. The vulnerability exists in the HTML writer component regardless of PHP version, but requires PhpSpreadsheet to be installed as a dependency.
How do I check if my server is vulnerable to CVE-2026-40296?
If using Composer, run `composer show phpoffice/phpspreadsheet` and check if the installed version is between 4.0.0 and 5.7.0 (exclusive). For PHP installations, verify PhpSpreadsheet is present in your project dependencies and compare against the vulnerable version ranges.
Does Defensia detect CVE-2026-40296?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If PhpSpreadsheet is present on a monitored server, CVE-2026-40296 will appear in your dashboard with remediation steps.
Related PHP CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-40296. Free for 1 server.
Get started free