CVE-2023-37912

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 1.5% (73rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.8 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2023-10-25) is not newer than that change (2024-11-21), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2023-2625 (ENISA EUVD) · GHSA-35j5-m29r-xfq5 (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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: 1.5%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

XWiki Rendering is a generic Rendering system that converts textual input in a given syntax into another syntax. Prior to version 14.10.6 of org.xwiki.platform:xwiki-core-rendering-macro-footnotes and org.xwiki.platform:xwiki-rendering-macro-footnotes and prior to version 15.1-rc-1 of org.xwiki.platform:xwiki-rendering-macro-footnotes, the footnote macro executed its content in a potentially different context than the one in which it was defined. In particular in combination with the include macro, this allows privilege escalation from a simple user account in XWiki to programming rights and thus remote code execution, impacting the confidentiality, integrity and availability of the whole XWiki installation. This vulnerability has been patched in XWiki 14.10.6 and 15.1-rc-1. There is no workaround apart from upgrading to a fixed version of the footnote macro.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
1.5%
EPSS %ILE
73rd
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 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 low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

October 25, 2023

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Nov 6, 2026
Patch available. Sources: github, github_commit.
Web page

Loading...

https://jira.xwiki.org/browse/XRENDERING-688
GitHub advisoryMentions a patch (unverified)

Privilege escalation via the footnote macro · Advisory · xwiki/xwiki-rendering · GitHub

https://github.com/xwiki/xwiki-rendering/security/advisories/GHSA-35j5-m29r-xfq5
GitHub commit Patch Available

commit 5f558b8fac8b (xwiki/xwiki-rendering)

Patch available: xwiki/xwiki-rendering xwiki-rendering-18.3.0 (contains commit 5f558b8fac8b)

https://github.com/xwiki/xwiki-rendering/commit/5f558b8fac8b716d19999225f38cb8ed0814116e

Vendor Advisories for CVE-2023-37912(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.xwiki.platform:xwiki-core-rendering-macro-footnotes @ 14.10.6 (fixes < 14.10.6)—ghsa
mavenorg.xwiki.rendering:xwiki-rendering-macro-footnotes @ 15.1-rc-1 (fixes >= 15.0-rc-1, < 15.1-rc-1)—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

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
org.xwiki.platform:xwiki-core-rendering-macro-footnotes—
  • every version up to 14.10.6: fixed in 14.10.6
—
org.xwiki.rendering:xwiki-rendering-macro-footnotes15.0, 15.0-rc-1
  • every version up to 14.10.6: fixed in 14.10.6
  • 15.0-rc-1 up to 15.1-rc-1: fixed in 15.1-rc-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 44× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 261 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 161 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 01:12 UTCEchelonGraph re-scored
  2. 2026-11-13 01:12 UTCGHSA enrichmentGHSA-35j5-m29r-xfq5 · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-11-12 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  4. 2026-11-12 00:19 UTCEchelonGraph re-scored
  5. 2026-11-12 00:19 UTCGHSA enrichmentGHSA-35j5-m29r-xfq5 · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-11-11 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  7. 2026-11-10 23:29 UTCEchelonGraph re-scored
  8. 2026-11-10 23:29 UTCGHSA enrichmentGHSA-35j5-m29r-xfq5 · GitHub severity HIGH · GitHub CVSS 8.8
  9. 2026-11-10 16:37 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  10. 2026-11-09 22:39 UTCEchelonGraph re-scored
  11. 2026-11-09 22:39 UTCGHSA enrichmentGHSA-35j5-m29r-xfq5 · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-11-09 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  13. 2026-11-08 21:49 UTCEchelonGraph re-scored
  14. 2026-11-08 21:49 UTCGHSA enrichmentGHSA-35j5-m29r-xfq5 · GitHub severity HIGH · GitHub CVSS 8.8
  15. 2026-11-08 16:34 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  16. 2026-11-07 20:59 UTCEchelonGraph re-scored
  17. 2026-11-07 20:59 UTCGHSA enrichmentGHSA-35j5-m29r-xfq5 · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-11-07 16:35 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  19. 2026-11-06 20:09 UTCEchelonGraph re-scored
  20. 2026-11-06 20:09 UTCGHSA enrichmentGHSA-35j5-m29r-xfq5 · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-11-06 16:31 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  22. 2026-11-05 19:18 UTCEchelonGraph re-scored
  23. 2026-11-05 19:18 UTCGHSA enrichmentGHSA-35j5-m29r-xfq5 · GitHub severity HIGH · GitHub CVSS 8.8
  24. 2026-11-05 16:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  25. 2026-11-04 18:28 UTCEchelonGraph re-scored
Show 74 more
  1. 2026-11-04 18:28 UTCGHSA enrichmentGHSA-35j5-m29r-xfq5 · GitHub severity HIGH · GitHub CVSS 8.8
  2. 2026-11-04 16:31 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  3. 2026-11-04 14:55 UTCOSV refresh
  4. 2026-11-03 17:38 UTCEchelonGraph re-scored
  5. 2026-11-03 17:38 UTCGHSA enrichmentGHSA-35j5-m29r-xfq5 · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-11-03 16:40 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  7. 2026-11-02 16:48 UTCEchelonGraph re-scored
  8. 2026-11-02 16:48 UTCGHSA enrichmentGHSA-35j5-m29r-xfq5 · GitHub severity HIGH · GitHub CVSS 8.8
  9. 2026-11-02 16:39 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  10. 2026-11-01 16:31 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  11. 2026-11-01 15:42 UTCGHSA enrichmentGHSA-35j5-m29r-xfq5 · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-11-01 08:19 UTCGHSA enrichmentGHSA-35j5-m29r-xfq5 · GitHub severity HIGH · GitHub CVSS 8.8
  13. 2026-11-01 08:19 UTCEchelonGraph re-scored
  14. 2026-10-31 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  15. 2026-10-31 14:52 UTCEchelonGraph re-scored
  16. 2026-10-30 16:31 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  17. 2026-10-30 14:02 UTCEchelonGraph re-scored
  18. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  19. 2026-10-29 13:13 UTCEchelonGraph re-scored
  20. 2026-10-28 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  21. 2026-10-28 12:20 UTCEchelonGraph re-scored
  22. 2026-10-27 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  23. 2026-10-27 11:30 UTCEchelonGraph re-scored
  24. 2026-10-26 16:28 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  25. 2026-10-25 17:38 UTCEchelonGraph re-scored
  26. 2026-10-25 16:29 UTCEPSS rescoreEPSS 1.2% · 69th percentile
  27. 2026-10-25 09:51 UTCEchelonGraph re-scored
  28. 2026-10-24 16:29 UTCEPSS rescoreEPSS 1.2% · 69th percentile
  29. 2026-10-24 09:01 UTCEchelonGraph re-scored
  30. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.2% · 69th percentile
  31. 2026-10-23 08:10 UTCEchelonGraph re-scored
  32. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.2% · 69th percentile
  33. 2026-10-22 07:17 UTCEchelonGraph re-scored
  34. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.2% · 69th percentile
  35. 2026-10-21 06:26 UTCEchelonGraph re-scored
  36. 2026-10-20 16:29 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  37. 2026-10-20 05:36 UTCEchelonGraph re-scored
  38. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  39. 2026-10-19 04:46 UTCEchelonGraph re-scored
  40. 2026-10-18 16:29 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  41. 2026-10-18 03:54 UTCEchelonGraph re-scored
  42. 2026-10-17 16:29 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  43. 2026-10-17 03:04 UTCEchelonGraph re-scored
  44. 2026-10-16 16:35 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  45. 2026-10-16 02:13 UTCEchelonGraph re-scored
  46. 2026-10-15 16:29 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  47. 2026-10-14 22:06 UTCEchelonGraph re-scored
  48. 2026-10-14 16:29 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  49. 2026-10-13 17:47 UTCEchelonGraph re-scored
  50. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  51. 2026-10-12 16:56 UTCEchelonGraph re-scored
  52. 2026-10-12 16:30 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  53. 2026-10-11 21:49 UTCEchelonGraph re-scored
  54. 2026-10-11 13:45 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  55. 2026-10-10 19:57 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  56. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  57. 2026-10-08 17:06 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  58. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  59. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  60. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  61. 2026-10-04 23:20 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  62. 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  63. 2026-09-30 16:27 UTCEchelonGraph re-scored
  64. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  65. 2026-09-29 15:16 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  66. 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  67. 2026-09-27 13:42 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  68. 2026-09-26 15:55 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  69. 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  70. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  71. 2026-09-23 13:45 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  72. 2026-09-22 18:38 UTCOSV refresh
  73. 2026-09-22 14:45 UTCEPSS rescoreEPSS 1.2% · 68th percentile
  74. 2026-09-20 20:14 UTCEPSS rescoreEPSS 1.2% · 67th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-37912?
CVE-2023-37912 is a critical-severity vulnerability; its CVE record was published on October 25, 2023. XWiki Rendering is a generic Rendering system that converts textual input in a given syntax into another syntax. Prior to version 14.10.6 of org.xwiki.platform:xwiki-core-rendering-macro-footnotes and org.xwiki.platform:xwiki-rendering-macro-footnotes and prior to version 15.1-rc-1 of…
When was the CVE record for CVE-2023-37912 published?
The CVE record for CVE-2023-37912 was published on October 25, 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-37912 actively exploited?
CVE-2023-37912 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (73rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-37912?
CVE-2023-37912 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2023-37912?
A fix for CVE-2023-37912 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-37912 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-37912

Explore →

Is Your Infrastructure Affected by CVE-2023-37912?

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

Book a Demo →Browse All CVEs