CVE-2023-45138

CRITICALNVD 9.610.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-10-17. NVD baseline CVSS 9.6; sources differ by 0.4.

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

Also known asEUVD-2023-2722 (ENISA EUVD) · GHSA-f776-w9v2-7vfj (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 72%
CISA-KEV: Not listedEPSS PROB: 72%CVSS: 9.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Change Request is an pplication allowing users to request changes on a wiki without publishing the changes directly. Starting in version 0.11 and prior to version 1.9.2, it's possible for a user without any specific right to perform script injection and remote code execution just by inserting an appropriate title when creating a new Change Request. This vulnerability is particularly critical as Change Request aims at being created by user without any particular rights. The vulnerability has been fixed in Change Request 1.9.2. It's possible to workaround the issue without upgrading by editing the document ChangeRequest.Code.ChangeRequestSheet and by performing the same change as in the fix commit.

CVSS v3
9.6
EG Score
10.0CRITICALmedium confidence
EG Risk
74
EG Risk 74/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.
Exploitation72% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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.
EPSS PROB
72%
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
72% 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 or medium mission impact; Track* at high (mission-essential systems).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 or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (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 12, 2023

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Oct 7, 2026
Patch available. Sources: github_commit, github.
Web page

Loading...

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

XSS and remote code execution through change request title · Advisory · xwiki-contrib/application-changerequest · GitHub

https://github.com/xwiki-contrib/application-changerequest/security/advisories/GHSA-f776-w9v2-7vfj
GitHub commit

commit 7565e720117f (xwiki-contrib/application-changerequest)

Fix landed in xwiki-contrib/application-changerequest commit 7565e720117f — awaiting tagged release

https://github.com/xwiki-contrib/application-changerequest/commit/7565e720117f73102f5a276239eabfe85e15cff4

Vendor Advisories for CVE-2023-45138(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.contrib.changerequest:application-changerequest-ui @ 1.9.2 (fixes >= 0.11, < 1.9.2)—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.contrib.changerequest:application-changerequest-ui—
  • 0.11 up to 1.9.2: fixed in 1.9.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× 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 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 195 rows on record for this CVE, as 96 entries (4 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 95 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-45138?
CVE-2023-45138 is a critical-severity vulnerability; its CVE record was published on October 12, 2023. Change Request is an pplication allowing users to request changes on a wiki without publishing the changes directly. Starting in version 0.11 and prior to version 1.9.2, it's possible for a user without any specific right to perform script injection and remote code execution just by inserting an…
When was the CVE record for CVE-2023-45138 published?
The CVE record for CVE-2023-45138 was published on October 12, 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-45138 actively exploited?
CVE-2023-45138 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 72% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-45138?
CVE-2023-45138 has a CVSS v3 base score of 9.6 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 10.0 (CRITICAL).
How do I remediate CVE-2023-45138?
A fix for CVE-2023-45138 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-45138 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-45138

Explore →

Is Your Infrastructure Affected by CVE-2023-45138?

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

Book a Demo →Browse All CVEs