CVE-2023-24814

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.8% (57th 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
Elevated
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

TYPO3 is a free and open source Content Management Framework released under the GNU General Public License. In affected versions the TYPO3 core component GeneralUtility::getIndpEnv() uses the unfiltered server environment variable PATH_INFO, which allows attackers to inject malicious content. In combination with the TypoScript setting config.absRefPrefix=auto, attackers can inject malicious HTML code to pages that have not been rendered and cached, yet. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting). Individual code which relies on the resolved value of GeneralUtility::getIndpEnv('SCRIPT_NAME') and corresponding usages (as shown below) are vulnerable as well. Additional investigations confirmed that at least Apache web server deployments using CGI (FPM, FCGI/FastCGI, and similar) are affected. However, there still might be the risk that other scenarios like nginx, IIS, or Apache/mod_php are vulnerable. The usage of server environment variable PATH_INFO has been removed from corresponding processings in GeneralUtility::getIndpEnv(). Besides that, the public property TypoScriptFrontendController::$absRefPrefix is encoded for both being used as a URI component and for being used as a prefix in an HTML context. This mitigates the cross-site scripting vulnerability. Users are advised to update to TYPO3 versions 8.7.51 ELTS, 9.5.40 ELTS, 10.4.35 LTS, 11.5.23 LTS and 12.2.0 which fix this problem. For users who are unable to patch in a timely manner the TypoScript setting config.absRefPrefix should at least be set to a static path value, instead of using auto - e.g. config.absRefPrefix=/. This workaround does not fix all aspects of the vulnerability, and is just considered to be an intermediate mitigation to the most prominent manifestation.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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.8%
EPSS %ILE
57th
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-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.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). 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 low or medium mission impact; Track* at high (mission-essential systems).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: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (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.

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

February 7, 2023

Last Modified

November 21, 2024

Advisory Details (6)

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

typo3/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php at v11.5.22 · TYPO3/typo3 · GitHub

https://github.com/TYPO3/typo3/blob/v11.5.22/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php#L2547-L2549
Web page

typo3/typo3/sysext/core/Classes/Utility/GeneralUtility.php at v11.5.22 · TYPO3/typo3 · GitHub

https://github.com/TYPO3/typo3/blob/v11.5.22/typo3/sysext/core/Classes/Utility/GeneralUtility.php#L2481-L2484
Web page

TYPO3-PSA-2023-001: Important Security-Bulletin Pre-Announcement - TYPO3 News

https://typo3.org/security/advisory/typo3-psa-2023-001
Web page

TYPO3-CORE-SA-2023-001: Persisted Cross-Site Scripting in Frontend Rendering - TYPO3 News

https://typo3.org/security/advisory/typo3-core-sa-2023-001
GitHub advisoryMentions a patch (unverified)

Persisted Cross-Site Scripting in Frontend Rendering · Advisory · TYPO3/typo3 · GitHub

https://github.com/TYPO3/typo3/security/advisories/GHSA-r4f8-f93x-5qh3
GitHub commit

commit 0005a6fd86ab (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit 0005a6fd86ab — awaiting tagged release

https://github.com/TYPO3/typo3/commit/0005a6fd86ab97eff8bf2e3a5828bf0e7cb6263a

Affected Packages

(2 across 1 ecosystem)
Packagist(2)
PackageVulnerable rangeFix by version rangeDependents
typo3/cmsv12.0.0, v12.1.0, v12.1.1, v12.1.2, v12.1.3
  • 10.0.0 up to 10.4.35: fixed in 10.4.35
  • 11.0.0 up to 11.5.23: fixed in 11.5.23
  • 12.0.0 up to 12.2.0: fixed in 12.2.0
—
typo3/cms-corev8.7.10 ... v8.7.9 (26 versions)
  • 12.0.0 up to 12.2.0: fixed in 12.2.0
  • 11.0.0 up to 11.5.23: fixed in 11.5.23
  • 10.0.0 up to 10.4.36: fixed in 10.4.36
  • 9.0.0 up to 9.5.40: fixed in 9.5.40
  • 8.7.0 up to 8.7.51: fixed in 8.7.51
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 33× 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 93 of 199 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 106 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2023-24814?
CVE-2023-24814 is a high-severity vulnerability; its CVE record was published on February 7, 2023. TYPO3 is a free and open source Content Management Framework released under the GNU General Public License. In affected versions the TYPO3 core component GeneralUtility::getIndpEnv() uses the unfiltered server environment variable PATHINFO, which allows attackers to inject malicious content. In…
When was the CVE record for CVE-2023-24814 published?
The CVE record for CVE-2023-24814 was published on February 7, 2023. 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-24814 actively exploited?
CVE-2023-24814 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-24814?
CVE-2023-24814 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2023-24814?
A fix for CVE-2023-24814 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-2023-24814

Explore →

Is Your Infrastructure Affected by CVE-2023-24814?

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