CVE-2026-35453

PhpSpreadsheet XSS via number format text substitution in HTML Writer

MEDIUM
5.4
CVSS Score
Published: May 5, 2026 at 07:39 PM UTC
Updated: July 24, 2026 at 09:20 PM UTC
1 product affected across 1 vendorPhpSpreadsheet

Using PhpSpreadsheet by PHPOffice?

Get instant alerts when new vulnerabilities affect PhpSpreadsheet - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.4
Exploit prediction
EPSS 0.2%
SSVC
PoC

Description

PhpSpreadsheet is a library for reading and writing spreadsheet files. In versions 1.30.3 and earlier, 2.0.0 through 2.1.15, 2.2.0 through 2.4.4, 3.3.0 through 3.10.4, and 4.0.0 through 5.6.0, the HTML Writer skips htmlspecialchars() output escaping when a cell uses a custom number format containing the @ text placeholder with additional literal text (e.g., @ "items"). The escaping is only applied when the formatted output strictly equals the original cell value. When the format code contains @ with quoted literal text, the formatter substitutes the raw cell value into the format string and returns early without invoking the escaping callback. An attacker who can control cell content in a spreadsheet processed by the HTML Writer can inject arbitrary HTML and JavaScript into the generated output. This issue has been fixed in versions 1.30.4, 2.1.16, 2.4.5, 3.10.5, and 5.7.0.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≤ 2.1.15v ≤ 2.4.4v ≤ 3.10.4v ≤ 5.6.0v < 1.30.42.0.0 ≤ v < 2.1.162.2.0 ≤ v < 2.4.53.3.0 ≤ v < 3.10.54.0.0 ≤ v < 5.7.0<= 1.30.3
Affected range stops below 1.30.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.1.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.4.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.10.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.7.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

x_refsource_CONFIRMExploitVendor Advisory
Source: cverecord
https://github.com/PHPOffice/PhpSpreadsheet/security/advisories/GHSA-6wpp-88cp-7q68

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
REQUIRED
Scope
CHANGED
Confidentiality
LOW
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-79

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card