CVE-2024-31464

MEDIUMNVD 6.86.8
EchelonGraph scoreMEDIUM confidence

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

Score 6.8 from GitHub Security Advisory (severity: MODERATE) published 2024-04-10. NVD baseline CVSS 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2024-1308 (ENISA EUVD) · GHSA-v782-xr4w-3vqx (GitHub Security Advisories)Source: ENISA EUVD

6.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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: 0.4%CVSS: 6.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

XWiki Platform is a generic wiki platform. Starting in version 5.0-rc-1 and prior to versions 14.10.19, 15.5.4, and 15.9-rc-1, it is possible to access the hash of a password by using the diff feature of the history whenever the object storing the password is deleted. Using that vulnerability it's possible for an attacker to have access to the hash password of a user if they have rights to edit the users' page. With the default right scheme in XWiki this vulnerability is normally prevented on user profiles, except by users with Admin rights. Note that this vulnerability also impacts any extensions that might use passwords stored in xobjects: for those usecases it depends on the right of those pages. There is currently no way to be 100% sure that this vulnerability has been exploited, as an attacker with enough privilege could have deleted the revision where the xobject was deleted after rolling-back the deletion. But again, this operation requires high privileges on the target page (Admin right). A page with a user password xobject which have in its history a revision where the object has been deleted should be considered at risk and the password should be changed there. a diff, to ensure it's not coming from a password field. As another mitigation, admins should ensure that the user pages are properly protected: the edit right shouldn't be allowed for other users than Admin and owner of the profile (which is the default right). There is not much workaround possible for a privileged user other than upgrading XWiki.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
47
EG Risk 47/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)
Severity68% × 45%
Impact severity (EG Severity): CVSS 6.8 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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
0.4%
EPSS %ILE
31st
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 (6.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.

EG Severity
6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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: 60 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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

April 10, 2024

Last Modified

January 9, 2025

Advisory Details (5)

Auto-updated Oct 24, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Password hash might be leaked by diff once the xobject holding them is deleted · Advisory · xwiki/xwiki-platform · GitHub

https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-v782-xr4w-3vqx
GitHub commit Patch Available

commit f1eaec1e5122 (xwiki/xwiki-platform)

Patch available: xwiki/xwiki-platform xwiki-platform-18.2.1 (contains commit f1eaec1e5122)

https://github.com/xwiki/xwiki-platform/commit/f1eaec1e512220fabd970d053c627e435a1652cf
GitHub commit

commit 955fb097e02a (xwiki/xwiki-platform)

Fix landed in xwiki/xwiki-platform commit 955fb097e02a — awaiting tagged release

https://github.com/xwiki/xwiki-platform/commit/955fb097e02a2a7153f527522ee9eef42447e5d7
GitHub commit

commit 9075668a4135 (xwiki/xwiki-platform)

Fix landed in xwiki/xwiki-platform commit 9075668a4135 — awaiting tagged release

https://github.com/xwiki/xwiki-platform/commit/9075668a4135cce114ef2a4b72eba3161a9e94c4

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.xwiki.platform:xwiki-platform-oldcore @ 14.10.19 (fixes >= 5.0-rc-1, < 14.10.19)—ghsa
mavenorg.xwiki.platform:xwiki-platform-oldcore @ 15.5.4 (fixes >= 15.0-rc-1, < 15.5.4)—ghsa
mavenorg.xwiki.platform:xwiki-platform-oldcore @ 15.9-rc-1 (fixes >= 15.6-rc-1, < 15.9-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.platform:xwiki-platform-oldcore—
  • 5.0-rc-1 up to 14.10.19: fixed in 14.10.19
  • 15.0-rc-1 up to 15.5.4: fixed in 15.5.4
  • 15.6-rc-1 up to 15.9-rc-1: fixed in 15.9-rc-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 38× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 94 of 219 refreshes 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 125 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-31464?
CVE-2024-31464 is a medium-severity vulnerability; its CVE record was published on April 10, 2024. XWiki Platform is a generic wiki platform. Starting in version 5.0-rc-1 and prior to versions 14.10.19, 15.5.4, and 15.9-rc-1, it is possible to access the hash of a password by using the diff feature of the history whenever the object storing the password is deleted. Using that vulnerability it's…
When was the CVE record for CVE-2024-31464 published?
The CVE record for CVE-2024-31464 was published on April 10, 2024. 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 January 9, 2025; the record at its source may have been updated since.
Is CVE-2024-31464 actively exploited?
CVE-2024-31464 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-31464?
CVE-2024-31464 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2024-31464?
A fix for CVE-2024-31464 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-31464

Explore →

Is Your Infrastructure Affected by CVE-2024-31464?

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