CVE-2023-36471

CRITICALNVD 9.09.0
EchelonGraph scoreMEDIUM confidence

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

Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2023-06-30. NVD baseline CVSS 9.0; sources differ by 0.0.

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

Also known asEUVD-2023-1714 (ENISA EUVD) · GHSA-6pqf-c99p-758v (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
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.0%CVSS: 9.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Xwiki commons is the common modules used by other XWiki top level projects. The HTML sanitizer that is included in XWiki since version 14.6RC1 allowed form and input HTML tags. In the context of XWiki, this allows an attacker without script right to either create forms that can be used for phishing attacks or also in the context of a sheet, the attacker could add an input like {{html}}{{/html}} that would allow remote code execution when it is submitted by an admin (the sheet is rendered as part of the edit form). The attacker would need to ensure that the edit form looks plausible, though, which can be non-trivial as without script right the attacker cannot display the regular content of the document. This has been patched in XWiki 14.10.6 and 15.2RC1 by removing the central form-related tags from the list of allowed tags. Users are advised to upgrade. As a workaround an admin can manually disallow the tags by adding form, input, select, textarea, button to the configuration option xml.htmlElementSanitizer.forbidTags in the xwiki.properties configuration file.

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

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

June 29, 2023

Last Modified

November 21, 2024

Advisory Details (3)

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

Loading...

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

HTML sanitizer allows form elements in restricted in org.xwiki.commons:xwiki-commons-xml · Advisory · xwiki/xwiki-commons · GitHub

https://github.com/xwiki/xwiki-commons/security/advisories/GHSA-6pqf-c99p-758v
GitHub commit Patch Available

commit 99484d48e899 (xwiki/xwiki-commons)

Patch available: xwiki/xwiki-commons xwiki-commons-17.4.8 (contains commit 99484d48e899)

https://github.com/xwiki/xwiki-commons/commit/99484d48e899a68a1b6e33d457825b776c6fe8c3

Vendor Advisories for CVE-2023-36471(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.commons:xwiki-commons-xml @ 14.10.6 (fixes >= 14.6-rc-1, < 14.10.6)—ghsa
mavenorg.xwiki.commons:xwiki-commons-xml @ 15.2-rc-1 (fixes >= 15.0-rc-1, < 15.2-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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.xwiki.commons:xwiki-commons-xml15.0, 15.0-rc-1, 15.1, 15.1-rc-1
  • 14.6-rc-1 up to 14.10.6: fixed in 14.10.6
  • 15.0-rc-1 up to 15.2-rc-1: fixed in 15.2-rc-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 45× 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 272 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 172 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.0% · 64th percentile
  2. 2026-11-13 10:53 UTCEchelonGraph re-scored
  3. 2026-11-13 10:53 UTCGHSA enrichmentGHSA-6pqf-c99p-758v · GitHub severity CRITICAL · GitHub CVSS 9.0
  4. 2026-11-12 16:30 UTCEPSS rescoreEPSS 1.0% · 64th percentile
  5. 2026-11-12 12:20 UTCEchelonGraph re-scored
  6. 2026-11-12 12:20 UTCGHSA enrichmentGHSA-6pqf-c99p-758v · GitHub severity CRITICAL · GitHub CVSS 9.0
  7. 2026-11-11 16:33 UTCEPSS rescoreEPSS 1.0% · 64th percentile
  8. 2026-11-11 13:46 UTCEchelonGraph re-scored
  9. 2026-11-11 13:46 UTCGHSA enrichmentGHSA-6pqf-c99p-758v · GitHub severity CRITICAL · GitHub CVSS 9.0
  10. 2026-11-10 16:37 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  11. 2026-11-10 15:12 UTCGHSA enrichmentGHSA-6pqf-c99p-758v · GitHub severity CRITICAL · GitHub CVSS 9.0
  12. 2026-11-09 16:39 UTCEchelonGraph re-scored
  13. 2026-11-09 16:39 UTCGHSA enrichmentGHSA-6pqf-c99p-758v · GitHub severity CRITICAL · GitHub CVSS 9.0
  14. 2026-11-09 16:30 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  15. 2026-11-08 18:05 UTCEchelonGraph re-scored
  16. 2026-11-08 18:05 UTCGHSA enrichmentGHSA-6pqf-c99p-758v · GitHub severity CRITICAL · GitHub CVSS 9.0
  17. 2026-11-08 16:34 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  18. 2026-11-07 19:31 UTCEchelonGraph re-scored
  19. 2026-11-07 19:31 UTCGHSA enrichmentGHSA-6pqf-c99p-758v · GitHub severity CRITICAL · GitHub CVSS 9.0
  20. 2026-11-07 16:35 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  21. 2026-11-06 20:57 UTCEchelonGraph re-scored
  22. 2026-11-06 20:57 UTCGHSA enrichmentGHSA-6pqf-c99p-758v · GitHub severity CRITICAL · GitHub CVSS 9.0
  23. 2026-11-06 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  24. 2026-11-05 22:23 UTCEchelonGraph re-scored
  25. 2026-11-05 22:23 UTCGHSA enrichmentGHSA-6pqf-c99p-758v · GitHub severity CRITICAL · GitHub CVSS 9.0
Show 74 more
  1. 2026-11-05 16:33 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  2. 2026-11-04 23:45 UTCEchelonGraph re-scored
  3. 2026-11-04 23:45 UTCGHSA enrichmentGHSA-6pqf-c99p-758v · GitHub severity CRITICAL · GitHub CVSS 9.0
  4. 2026-11-04 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  5. 2026-11-04 14:25 UTCOSV refresh
  6. 2026-11-04 01:11 UTCEchelonGraph re-scored
  7. 2026-11-04 01:11 UTCGHSA enrichmentGHSA-6pqf-c99p-758v · GitHub severity CRITICAL · GitHub CVSS 9.0
  8. 2026-11-03 16:40 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  9. 2026-11-03 02:33 UTCEchelonGraph re-scored
  10. 2026-11-03 02:33 UTCGHSA enrichmentGHSA-6pqf-c99p-758v · GitHub severity CRITICAL · GitHub CVSS 9.0
  11. 2026-11-02 16:39 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  12. 2026-11-02 03:59 UTCEchelonGraph re-scored
  13. 2026-11-02 03:59 UTCGHSA enrichmentGHSA-6pqf-c99p-758v · GitHub severity CRITICAL · GitHub CVSS 9.0
  14. 2026-11-01 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  15. 2026-11-01 08:20 UTCGHSA enrichmentGHSA-6pqf-c99p-758v · GitHub severity CRITICAL · GitHub CVSS 9.0
  16. 2026-11-01 08:20 UTCEchelonGraph re-scored
  17. 2026-11-01 05:26 UTCEchelonGraph re-scored
  18. 2026-10-31 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  19. 2026-10-31 06:52 UTCEchelonGraph re-scored
  20. 2026-10-30 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  21. 2026-10-30 08:19 UTCEchelonGraph re-scored
  22. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  23. 2026-10-29 09:46 UTCEchelonGraph re-scored
  24. 2026-10-28 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  25. 2026-10-28 11:11 UTCEchelonGraph re-scored
  26. 2026-10-27 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  27. 2026-10-27 11:57 UTCEchelonGraph re-scored
  28. 2026-10-26 16:28 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  29. 2026-10-26 13:24 UTCEchelonGraph re-scored
  30. 2026-10-25 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  31. 2026-10-25 14:38 UTCEchelonGraph re-scored
  32. 2026-10-24 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  33. 2026-10-23 17:25 UTCEchelonGraph re-scored
  34. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  35. 2026-10-22 18:51 UTCEchelonGraph re-scored
  36. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  37. 2026-10-21 20:17 UTCEchelonGraph re-scored
  38. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  39. 2026-10-20 21:43 UTCEchelonGraph re-scored
  40. 2026-10-20 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  41. 2026-10-19 23:10 UTCEchelonGraph re-scored
  42. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  43. 2026-10-18 22:35 UTCEchelonGraph re-scored
  44. 2026-10-18 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  45. 2026-10-18 07:57 UTCEchelonGraph re-scored
  46. 2026-10-17 23:17 UTCEchelonGraph re-scored
  47. 2026-10-17 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  48. 2026-10-17 00:42 UTCEchelonGraph re-scored
  49. 2026-10-16 16:35 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  50. 2026-10-16 00:35 UTCEchelonGraph re-scored
  51. 2026-10-15 16:29 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  52. 2026-10-14 19:12 UTCEchelonGraph re-scored
  53. 2026-10-14 16:29 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  54. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  55. 2026-10-12 16:59 UTCEchelonGraph re-scored
  56. 2026-10-12 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  57. 2026-10-11 21:50 UTCEchelonGraph re-scored
  58. 2026-10-11 13:45 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  59. 2026-10-10 19:57 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  60. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  61. 2026-10-08 17:06 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  62. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  63. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  64. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  65. 2026-10-04 23:20 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  66. 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  67. 2026-09-30 16:26 UTCEchelonGraph re-scored
  68. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  69. 2026-09-29 15:16 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  70. 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  71. 2026-09-27 13:42 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  72. 2026-09-26 15:55 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  73. 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  74. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.0% · 62nd percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2023-36471?
CVE-2023-36471 is a critical-severity vulnerability; its CVE record was published on June 29, 2023. Xwiki commons is the common modules used by other XWiki top level projects. The HTML sanitizer that is included in XWiki since version 14.6RC1 allowed form and input HTML tags. In the context of XWiki, this allows an attacker without script right to either create forms that can be used for phishing…
When was the CVE record for CVE-2023-36471 published?
The CVE record for CVE-2023-36471 was published on June 29, 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-36471 actively exploited?
CVE-2023-36471 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (64th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-36471?
CVE-2023-36471 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2023-36471?
A fix for CVE-2023-36471 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-36471 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-36471

Explore →

Is Your Infrastructure Affected by CVE-2023-36471?

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

Book a Demo →Browse All CVEs