CVE-2026-40296: PhpSpreadsheet vulnerable to XSS in HTML writer via custom number format codes

Published Apr 28, 2026
·
Updated

It was discovered that there is a way to bypass HTML escaping in the HTML writer using custom number format codes.

The Problem

In Writer/Html.php around line 1592, the code checks if the formatted cell data equals the original data to decide whether to apply htmlspecialchars():

php if ($cellData === $origData) { $cellData = htmlspecialchars($cellData, ...); }

When a cell has a custom number format containing @ (text placeholder) with any additional literal characters, the formatter replaces @ with the cell value and adds the extra characters. This makes $cellData !== $origData, so htmlspecialchars() is skipped entirely.

Even a single trailing space in the format (@ ) is enough to bypass the escape.

Proof of Concept

php use PhpOffice\PhpSpreadsheet\Spreadsheet; use PhpOffice\PhpSpreadsheet\Writer\Html; use PhpOffice\PhpSpreadsheet\Cell\DataType;

$spreadsheet = new Spreadsheet(); $sheet = $spreadsheet->getActiveSheet();

// XSS payload with malicious number format $sheet->setCellValueExplicit('A1', '<img src=x onerror=alert(document.cookie)>', DataType::TYPESTRING); $sheet->getStyle('A1')->getNumberFormat()->setFormatCode('. @');

$writer = new Html($spreadsheet); $writer->save('output.html');

The generated HTML contains: html <td>. <img src=x onerror=alert(document.cookie)></td>

The XSS payload is completely unescaped.

Tested Bypass Formats

| Format Code | Result | Escaped? | |---|---|---| | General (default) | Original value | YES (safe) | | . @ | . + value | NO (XSS!) | | @ (trailing space) | value + | NO (XSS!) | | x@ | x + value | NO (XSS!) |

This was tested with PhpSpreadsheet 4.5.0 and confirmed the XSS executes in the browser.

Impact

Any application that: 1. Accepts uploaded XLSX files from users 2. Converts them to HTML using PhpSpreadsheet's HTML writer 3. Displays the HTML to other users

...is vulnerable to stored XSS. The attacker embeds the payload in a cell value and sets a custom number format in the XLSX file's xl/styles.xml.

Suggested Fix

Always apply htmlspecialchars() regardless of whether formatting changed the value:

php // Instead of conditional escaping: $cellData = htmlspecialchars($cellData, ENTQUOTES | ENTSUBSTITUTE, 'UTF-8');

Or escape AFTER formatting, not conditionally based on equality.

Reporter Keyvan Hardani

Other sources

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.

MITRE

Affected Software

10 affected componentsFixes available
composer/phpoffice/phpspreadsheet<=1.30.3
1.30.4
composer/phpoffice/phpspreadsheet>=2.0.0<=2.1.15
2.1.16
composer/phpoffice/phpspreadsheet>=2.2.0<=2.4.4
2.4.5
composer/phpoffice/phpspreadsheet>=3.3.0<=3.10.4
3.10.5
composer/phpoffice/phpspreadsheet>=4.0.0<=5.6.0
5.7.0
PHPOffice phpspreadsheet<1.30.4
PHPOffice phpspreadsheet>=2.0.0<2.1.16
PHPOffice phpspreadsheet>=2.2.0<2.4.5
PHPOffice phpspreadsheet>=3.3.0<3.10.5
PHPOffice phpspreadsheet>=4.0.0<5.7.0

Event History

Apr 28, 2026
Advisory Published
via GitHub·10:57 PM
Data Sourced
via GitHub·10:57 PM
DescriptionSeverityWeaknessAffected Software
May 6, 2026
CVE Published
via MITRE·08:48 PM
Data Sourced
via MITRE·08:48 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-40296?

CVE-2026-40296 has been classified as a high severity vulnerability.

2

How do I fix CVE-2026-40296?

To fix CVE-2026-40296, upgrade to PhpSpreadsheet versions 1.30.4, 2.1.16, 2.4.5, 3.10.5, or 5.7.0.

3

What is the impact of CVE-2026-40296?

CVE-2026-40296 allows attackers to bypass HTML escaping, potentially leading to cross-site scripting attacks.

4

Which software versions are affected by CVE-2026-40296?

Affected versions include PhpSpreadsheet 1.30.3 and below, 2.1.15 and below, 2.4.4 and below, 3.10.4 and below, and 5.6.0 and below.

5

How does CVE-2026-40296 exploit HTML escaping?

CVE-2026-40296 exploits a flaw where custom number format codes can bypass the expected HTML escaping in the HTML writer.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203