vciy

CVE-2024-45293

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

XML External Entity Reference (XXE) in PHPSpreadsheet's XLSX reader

CVE-2024-452934 of 4 sources documented this
32

rank 32 = 1 + 19 + 7 + 5 + 0

rank@v1 · scheduled

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.02776  ·  without this subject the record ranks 31

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.5, from NVD  ·  without this subject the record ranks 13

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-11-21  ·  without this subject the record ranks 25

How much of the world it touches

NVD CPE configurations

3 products in the CPE ranges  ·  without this subject the record ranks 27

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 32

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$84,800over the next 30 days, if this record is yours
Movement+$1.54Mon 2025-11-21, the last material move, 9 months before this reading
Basisassumeda published average, not your estate

$84,800 = $4.99M incident cost x 0.6121449559255632 exposure x 0.02776 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.02776EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2026-06-15, 94 days at 0.03, as of 2026-09-17. arc-rules@v1

Foresight · where to check next

CVE-2019-13608North GridCVE-2016-9563geoserverCVE-2019-9670SysAid On-Prem45293

This record is one instance of CWE-611, improper restriction of xml external entity reference. The index holds 1328 prior instances of this class, 8 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running PHPOffice PhpSpreadsheet? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-611 Improper Restriction of XML External Entity Referencereceipt
Published consequencesCWE-611: Confidentiality: Read Application Data, Read Files or Directories; Integrity: Bypass Protection Mechanism; Availability: DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory)[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchphpspreadsheet 1.29.1; phpspreadsheet 2.1.1; phpspreadsheet 2.3.0receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA7.5 HIGHreceipt
CVSS, NVD7.5 HIGHreceipt
Exploit probability0.02776 · top 14% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byGitHub_Mreceipt
Recorded changes23 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productPHPOffice PhpSpreadsheetreceipt
Published rangesphpoffice phpspreadsheet < 1.29.1; phpoffice phpspreadsheet >= 2.0.0 < 2.1.1; phpoffice phpspreadsheet >= 2.2.0 < 2.3.0receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

Attack path

Unauthenticated network requestno credentials, no interactionPHPOffice PhpSpreadsheetCWE-611 XML external entity refer…Confidentiality lossC:Hexploits CWE-611data compromise

What it is stated by the CNA

PHPSpreadsheet is a pure PHP library for reading and writing spreadsheet files. The security scanner responsible for preventing XXE attacks in the XLSX reader can be bypassed by slightly modifying the XML structure, utilizing white-spaces. On servers that allow users to upload their own Excel (XLSX) sheets, Server files and sensitive information can be disclosed by providing a crafted sheet. The security scan function in src/PhpSpreadsheet/Reader/Security/XmlScanner.php contains a flawed XML encoding check to retrieve the input file's XML encoding in the toUtf8 function. receipt

Read the rest of the CNA's description

The function searches for the XML encoding through a defined regex which looks for `encoding="*"` and/or `encoding='*'`, if not found, it defaults to the UTF-8 encoding which bypasses the conversion logic. This logic can be used to pass a UTF-7 encoded XXE payload, by utilizing a whitespace before or after the = in the attribute definition. Sensitive information disclosure through the XXE on sites that allow users to upload their own excel spreadsheets, and parse them using PHPSpreadsheet's Excel parser. This issue has been addressed in release versions 1.29.1, 2.1.1, and 2.3.0. All users are advised to upgrade. There are no known workarounds for this vulnerability.

NVD's analysis a second authority

severity
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
weakness
CWE-611
affected versions
phpoffice phpspreadsheet < 1.29.1; phpoffice phpspreadsheet >= 2.0.0 < 2.1.1; phpoffice phpspreadsheet >= 2.2.0 < 2.3.0
also scored by
[email protected] 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

check it yourself github.com receipt

Dated events

2025-03-17EPSS moved 0.01 to 0.162026-06-15EPSS moved 0.72 to 0.03

Movement the material steps

8 Oct 20240.00043
17 Mar 20250.16467 · crossed 0.10 · scoring model v2025.03.14
18 Mar 20250.09861 · crossed 0.10
23 Mar 20250.16467 · crossed 0.10
24 Mar 20250.09861 · crossed 0.10
28 Mar 20250.16467 · crossed 0.10
29 Mar 20250.61261 · crossed 0.50
30 Mar 20250.16467 · crossed 0.50
15 Nov 20250.66826 · crossed 0.50
18 Nov 20250.16467 · crossed 0.50
21 Nov 20250.66826 · crossed 0.50
15 Jun 20260.02859 · crossed 0.10 and 0.50 · scoring model v2026.06.15
17 Sep 20260.02776

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 23 observations
8 Oct 20240.00043
12 Dec 20240.00053
8 Mar 20250.01336
12 Mar 20250.01094
17 Mar 20250.16467
18 Mar 20250.09861
23 Mar 20250.16467
24 Mar 20250.09861
28 Mar 20250.16467
29 Mar 20250.61261
30 Mar 20250.16467
15 Apr 20250.21472
15 Nov 20250.66826
18 Nov 20250.16467
21 Nov 20250.66826
30 Nov 20250.65316
13 Feb 20260.6683
26 Feb 20260.71632
29 Apr 20260.70311
12 May 20260.71632
15 Jun 20260.02859
14 Jul 20260.02799
17 Sep 20260.02776

23 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.02776Published2024-10-07Index as of2026-09-17

Exploit probability more than doubled between 2025-03-28 and 2025-03-29 (0.16467 → 0.61261) and the record had been public for 1 year, 11 months when this index was last written.

Published 2024-10-07 receipt · Index as of 2026-09-17 derived

The pattern, elsewhere

This record is one instance of CWE-611, improper restriction of xml external entity reference. The index holds 1328 prior instances of this class, 8 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2019-13608matches 8 of 8KEV listed · 2019receipt
CVE-2023-45727 · North Grid Corporation Proself…matches 8 of 9KEV listed · 2023receipt
CVE-2016-9563matches 7 of 8KEV listed · 2016receipt
CVE-2025-58360 · geoservermatches 7 of 9KEV listed · 2025receipt
CVE-2019-9670matches 6 of 8KEV listed · 2019receipt
CVE-2025-2775 · SysAid On-Premmatches 6 of 9KEV listed · 2025receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

1328 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

phpoffice phpspreadsheet

Of the 4 records in this family that state one, this holds the highest EPSS percentile: 0.85496.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2024-45293.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.