CVE-2023-46731

CRITICALNVD 9.810.0
EchelonGraph scoreMEDIUM confidence

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

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2023-11-08. NVD baseline CVSS 9.8; sources differ by 0.2.

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

Also known asEUVD-2023-2893 (ENISA EUVD) · GHSA-62pr-qqf7-hh89 (GitHub Security Advisories)Source: ENISA EUVD

10.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).
  • High exploitation likelihood — EPSS 90%
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 90%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. XWiki doesn't properly escape the section URL parameter that is used in the code for displaying administration sections. This allows any user with read access to the document XWiki.AdminSheet (by default, everyone including unauthenticated users) to execute code including Groovy code. This impacts the confidentiality, integrity and availability of the whole XWiki instance. This vulnerability has been patched in XWiki 14.10.14, 15.6 RC1 and 15.5.1. Users are advised to upgrade. Users unablr to upgrade may apply the fix in commit fec8e0e53f9 manually. Alternatively, to protect against attacks from unauthenticated users, view right for guests can be removed from this document (it is only needed for space and wiki admins).

CVSS v3
9.8
EG Score
10.0CRITICALmedium confidence
EG Risk
96
EG Risk 96/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation90% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (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 yes (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
90%
EPSS %ILE
99th
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
90% 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: 3 days if the affected system is publicly exposed; 60 days 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 yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

November 6, 2023

Last Modified

June 17, 2026

Advisory Details (4)

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

Loading...

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

Remote code execution through the section parameter in Administration as guest · Advisory · xwiki/xwiki-platform · GitHub

https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-62pr-qqf7-hh89
GitHub commit Patch Available

commit fec8e0e53f9f (xwiki/xwiki-platform)

Patch available: xwiki/xwiki-platform xwiki-platform-18.3.0-rc-1 (contains commit fec8e0e53f9f)

https://github.com/xwiki/xwiki-platform/commit/fec8e0e53f9fa2c3f1e568cc15b0e972727c803a#diff-6271f9be501f30b2ba55459eb451aee3413d34171ba8198a77c865306d174e23
GitHub commit Patch Available

commit fec8e0e53f9f (xwiki/xwiki-platform)

Patch available: xwiki/xwiki-platform xwiki-platform-18.3.0-rc-1 (contains commit fec8e0e53f9f)

https://github.com/xwiki/xwiki-platform/commit/fec8e0e53f9fa2c3f1e568cc15b0e972727c803a

Vendor Advisories for CVE-2023-46731(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-platform-administration @ 14.10.14 (fixes < 14.10.14)—ghsa
mavenorg.xwiki.platform:xwiki-platform-administration-ui @ 15.5.1 (fixes >= 15.0-rc-1, < 15.5.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-platform-administration—
  • every version up to 14.10.14: fixed in 14.10.14
—
org.xwiki.platform:xwiki-platform-administration-ui—
  • every version up to 14.10.14: fixed in 14.10.14
  • 15.0-rc-1 up to 15.5.1: fixed in 15.5.1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 24× 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 147 rows on record for this CVE, as 95 entries (5 repeats 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 47 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2023-46731?
CVE-2023-46731 is a critical-severity vulnerability; its CVE record was published on November 6, 2023. XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. XWiki doesn't properly escape the section URL parameter that is used in the code for displaying administration sections. This allows any user with read access to the document XWiki.AdminSheet…
When was the CVE record for CVE-2023-46731 published?
The CVE record for CVE-2023-46731 was published on November 6, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2023-46731 actively exploited?
CVE-2023-46731 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 90% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-46731?
CVE-2023-46731 has a CVSS v3 base score of 9.8 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 10.0 (CRITICAL).
How do I remediate CVE-2023-46731?
A fix for CVE-2023-46731 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-46731 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-46731

Explore →

Is Your Infrastructure Affected by CVE-2023-46731?

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

Book a Demo →Browse All CVEs