vciy

CVE-2021-21707

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.

Special characters break path parsing in XML functions

CVE-2021-217074 of 4 sources documented this
38

rank 38 = 19 + 13 + 0 + 6 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.25951  ·  without this subject the record ranks 19

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.3, from NVD  ·  without this subject the record ranks 25

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 38

How much of the world it touches

NVD CPE configurations

6 products in the CPE ranges  ·  without this subject the record ranks 32

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$311,000over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$311,000 = $4.99M incident cost x 0.24048551839932833 exposure x 0.25951 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.25951EPSSNOT IN KEVas of 2026-09-20
Severity5.3 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationpublic proof-of-conceptreceipt
Defensefix version namedreceipt
Movementthreshold crossedreceipt
RISING10Risen from 0.00416 to 0.25951 across 41 observations. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running PHP? 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
ImpactPartial confidentiality lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-159 Improper Handling of Invalid Use of Special Elementsreceipt
Published consequencesCWE-159: Integrity: Unexpected State[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed in7.3.33; 7.4.26; 8.0.13receipt
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: Proof-of-concept published · 1 public repository, 2025-09-08.

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

Authority who says so

CVSS, the CNA5.3 MEDIUMreceipt
CVSS, NVD5.3 MEDIUMreceipt
Exploit probability0.25951 · top 2% of all CVEsreceipt
Blast breadth3 products across 3 vendorsderived
Assigned byphpreceipt
Recorded changes44 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productPHP Group PHPreceipt
Published rangesphp >= 7.3.0 < 7.3.33; php >= 7.4.0 < 7.4.26; php >= 8.0.0 < 8.0.13; debian linux 10.0receipt
Show all 6 published ranges
php >= 7.3.0 < 7.3.33
php >= 7.4.0 < 7.4.26
php >= 8.0.0 < 8.0.13
debian linux 10.0
debian linux 11.0
tenable.sc < 5.21.0
Fixed in7.3.33; 7.4.26; 8.0.13receipt

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.

What it is stated by the CNA

In PHP versions 7.3.x below 7.3.33, 7.4.x below 7.4.26 and 8.0.x below 8.0.13, certain XML parsing functions, like simplexml_load_file(), URL-decode the filename passed to them. If that filename contains URL-encoded NUL character, this may cause the function to interpret this as the end of the filename, thus interpreting the filename differently from what the user intended, which may lead it to reading a different file than intended. receipt

NVD's analysis a second authority

severity
5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
weakness
CWE-159
affected versions
php >= 7.3.0 < 7.3.33; php >= 7.4.0 < 7.4.26; php >= 8.0.0 < 8.0.13; and 3 more, listed in full below
also scored by
[email protected] 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

check it yourself bugs.php.net security.netapp.com debian.org tenable.com lists.debian.org receipt

Movement the material steps

29 Nov 20210.00416
7 Mar 20237.1e-4 · scoring model v2023.03.01
17 Mar 20250.00638 · scoring model v2025.03.14
15 Jun 20260.25951 · crossed 0.10 · scoring model v2026.06.15
Show all 41 observations
29 Nov 20210.00416
24 Dec 20210.00624
6 Jan 20220.02742
4 Feb 20220.04499
22 Feb 20220.05736
1 Apr 20220.00954
21 Apr 20220.01018
7 Mar 20237.1e-4
8 Mar 20230.00071
8 May 20230.00077
12 May 20230.00110
9 Jun 20230.00077
22 Jun 20230.00087
8 Feb 20240.00113
21 Jun 20240.00137
31 Jul 20240.00156
7 Oct 20240.00221
16 Dec 20240.00314
17 Dec 20240.00172
17 Mar 20250.00638
29 Mar 20250.00607
30 Mar 20250.00638
19 May 20250.00922
30 Jul 20250.00662
16 Aug 20250.00597
24 Aug 20250.00662
28 Aug 20250.00597
10 Sep 20250.00662
16 Sep 20250.00391
29 Sep 20250.00446
1 Oct 20250.00622
11 Oct 20250.00843
27 Oct 20250.00605
28 Oct 20250.00843
18 Nov 20250.01039
21 Nov 20250.00843
16 Dec 20250.00814
27 Dec 20250.00584
28 Dec 20250.00814
30 Dec 20250.00563
15 Jun 20260.25951

41 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.25951Published2021-11-29Public PoC2025-09-08Index as of2026-06-15

The record had been public for 4 years, 6 months when this index was last written.

Published 2021-11-29 receipt · Public PoC 2025-09-08 receipt · Index as of 2026-06-15 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2021-21707.

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.