CVE-2025-59020

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3% (24th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-2090 (ENISA EUVD) · GHSA-5j7q-wmh7-cqhg (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

By exploiting the defVals parameter, attackers could bypass field‑level access checks during record creation in the TYPO3 backend. This gave them the ability to insert arbitrary data into prohibited exclude fields of a database table for which the user already has write permission for a reduced set of fields. This issue affects TYPO3 CMS versions 10.0.0-10.4.54, 11.0.0-11.5.48, 12.0.0-12.4.40, 13.0.0-13.4.22 and 14.0.0-14.0.1.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 13, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 8, 2026
Patch available. Sources: github_commit.
Web page

TYPO3-CORE-SA-2026-001: Broken Access Control in Edit Document Controller - TYPO3 News

https://typo3.org/security/advisory/typo3-core-sa-2026-001
GitHub commit

commit fb98378a8fd3 (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit fb98378a8fd3 — awaiting tagged release

https://github.com/TYPO3/typo3/commit/fb98378a8fd30dd50d89a3d1a420780819f38232
GitHub commit

commit cd11a19958d8 (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit cd11a19958d8 — awaiting tagged release

https://github.com/TYPO3/typo3/commit/cd11a19958d823d12d028f9345b41739c7e70118
GitHub commit

commit ac3f792bd5ab (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit ac3f792bd5ab — awaiting tagged release

https://github.com/TYPO3/typo3/commit/ac3f792bd5ab7c58153fc1075cb9e001c9cebe3b

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composertypo3/cms-backend @ 14.0.2 (fixes >= 14.0.0, <= 14.0.1)—ghsa
composertypo3/cms-backend @ 13.4.23 (fixes >= 13.0.0, <= 13.4.22)—ghsa
composertypo3/cms-backend @ 12.4.41 (fixes >= 12.0.0, <= 12.4.40)—ghsa
composertypo3/cms-backend @ 11.5.49 (fixes >= 11.0.0, <= 11.5.48)—ghsa
composertypo3/cms-backend @ 10.4.55 (fixes >= 10.0.0, <= 10.4.54)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
typo3/cms-backendv10.0.0 ... v10.4.9 (43 versions)
  • 14.0.0 up to 14.0.2: fixed in 14.0.2
  • 13.0.0 up to 13.4.23: fixed in 13.4.23
  • 12.0.0 up to 12.4.41: fixed in 12.4.41
  • 11.0.0 up to 11.5.49: fixed in 11.5.49
  • 10.0.0 up to 10.4.55: fixed in 10.4.55
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 202 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 107 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  3. 2026-11-01 08:03 UTCGHSA enrichmentGHSA-5j7q-wmh7-cqhg · GitHub severity MODERATE
  4. 2026-11-01 08:03 UTCEG score recompute
  5. 2026-10-31 21:55 UTCOSV refresh
  6. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  7. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  8. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-10-25 16:16 UTCEG score recompute
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-23 16:25 UTCEG score recompute
  17. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-10-18 05:23 UTCEG score recompute
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
Show 70 more
  1. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-10-12 16:54 UTCEG score recompute
  4. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  5. 2026-10-11 20:28 UTCEG score recompute
  6. 2026-10-11 18:39 UTCEG score recompute
  7. 2026-10-11 15:15 UTCEG score recompute
  8. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-10-08 21:58 UTCOSV refresh
  12. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-09-26 00:25 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  25. 2026-09-21 21:06 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  26. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  27. 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  28. 2026-09-19 04:36 UTCOSV refresh
  29. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  30. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  31. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  32. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  33. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  34. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  35. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  36. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  37. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  38. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  39. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  40. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  41. 2026-09-05 15:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  42. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  43. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  44. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  45. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  46. 2026-08-31 08:25 UTCOSV refresh
  47. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  48. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  49. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  50. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  51. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  52. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  53. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  54. 2026-08-24 09:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  55. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  56. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  57. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  58. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  59. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  60. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  61. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  62. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  63. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  64. 2026-08-14 14:49 UTCEG score recompute
  65. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  66. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  67. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  68. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  69. 2026-08-09 20:26 UTCEG score recompute
  70. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-59020?
CVE-2025-59020 is a medium-severity vulnerability; its CVE record was published on January 13, 2026. By exploiting the defVals parameter, attackers could bypass field‑level access checks during record creation in the TYPO3 backend. This gave them the ability to insert arbitrary data into prohibited exclude fields of a database table for which the user already has write permission for a reduced set…
When was the CVE record for CVE-2025-59020 published?
The CVE record for CVE-2025-59020 was published on January 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2025-59020 actively exploited?
CVE-2025-59020 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-59020?
CVE-2025-59020 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2025-59020?
A fix for CVE-2025-59020 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-59020

Explore →

Is Your Infrastructure Affected by CVE-2025-59020?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs