CVE-2023-37908

CRITICALNVD 9.09.6
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2023-10-25. NVD baseline CVSS 9.0; sources differ by 0.6.

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

Also known asEUVD-2023-2666 (ENISA EUVD) · GHSA-663w-2xp3-5739 (GitHub Security Advisories)Source: ENISA EUVD

9.6EG
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.1%CVSS: 9.0Exploit: 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. The cleaning of attributes during XHTML rendering, introduced in version 14.6-rc-1, allowed the injection of arbitrary HTML code and thus cross-site scripting via invalid attribute names. This can be exploited, e.g., via the link syntax in any content that supports XWiki syntax like comments in XWiki. When a user moves the mouse over a malicious link, the malicious JavaScript code is executed in the context of the user session. When this user is a privileged user who has programming rights, this allows server-side code execution with programming rights, impacting the confidentiality, integrity and availability of the XWiki instance. While this attribute was correctly recognized as not allowed, the attribute was still printed with a prefix data-xwiki-translated-attribute- without further cleaning or validation. This problem has been patched in XWiki 14.10.4 and 15.0 RC1 by removing characters not allowed in data attributes and then validating the cleaned attribute again. There are no known workarounds apart from upgrading to a version including the fix.

CVSS v3
9.0
EG Score
9.6CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 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.1%
EPSS %ILE
66th
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.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.1% 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 (4)

Auto-updated Jul 26, 2026
Patch available. Sources: github_commit, github.
Web page

Loading...

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

Improper Neutralization of Script in Attributes in XWiki (X)HTML renderers · Advisory · xwiki/xwiki-rendering · GitHub

https://github.com/xwiki/xwiki-rendering/security/advisories/GHSA-6gf5-c898-7rxp
GitHub advisoryMentions a patch (unverified)

Improper Neutralization of Invalid Characters in Identifiers in Web Pages in org.xwiki.rendering:xwiki-rendering-xml · Advisory · xwiki/xwiki-rendering · GitHub

https://github.com/xwiki/xwiki-rendering/security/advisories/GHSA-663w-2xp3-5739
GitHub commit Patch Available

commit f4d5acac451d (xwiki/xwiki-rendering)

Patch available: xwiki/xwiki-rendering xwiki-rendering-17.4.8 (contains commit f4d5acac451d)

https://github.com/xwiki/xwiki-rendering/commit/f4d5acac451dccaf276e69f0b49b72221eef5d2f

Vendor Advisories for CVE-2023-37908(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.xwiki.rendering:xwiki-rendering-xml @ 14.10.4 (fixes >= 14.6-rc-1, < 14.10.4)—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)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.xwiki.rendering:xwiki-rendering-xml14.10 ... 14.9-rc-1 (12 versions)
  • 14.6-rc-1 up to 14.10.4: fixed in 14.10.4
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 46× 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 274 rows 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. None are among the latest 100 rows. The 174 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Same product

2 shown

Maven:org.xwiki.rendering:xwiki-rendering-xml

Frequently asked(5)

What is CVE-2023-37908?
CVE-2023-37908 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. The cleaning of attributes during XHTML rendering, introduced in version 14.6-rc-1, allowed the injection of arbitrary HTML code and thus cross-site scripting via invalid attribute…
When was the CVE record for CVE-2023-37908 published?
The CVE record for CVE-2023-37908 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-37908 actively exploited?
CVE-2023-37908 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-37908?
CVE-2023-37908 has a CVSS v3 base score of 9.0 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.6 (CRITICAL).
How do I remediate CVE-2023-37908?
A fix for CVE-2023-37908 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-37908 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-37908

Explore →

Is Your Infrastructure Affected by CVE-2023-37908?

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

Book a Demo →Browse All CVEs