CVE-2023-50719

CRITICALNVD 7.59.0
EchelonGraph scoreHIGH confidence

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

Score elevated to 9.0 because EPSS predicted 84% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2023-3256 (ENISA EUVD) · GHSA-p6cp-6r35-32mh (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).
  • High exploitation likelihood — EPSS 84%
CISA-KEV: Not listedEPSS PROB: 84%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

XWiki Platform is a generic wiki platform. Starting in 7.2-milestone-2 and prior to versions 14.10.15, 15.5.2, and 15.7-rc-1, the Solr-based search in XWiki discloses the password hashes of all users to anyone with view right on the respective user profiles. By default, all user profiles are public. This vulnerability also affects any configurations used by extensions that contain passwords like API keys that are viewable for the attacker. Normally, such passwords aren't accessible but this vulnerability would disclose them as plain text. This has been patched in XWiki 14.10.15, 15.5.2 and 15.7RC1. There are no known workarounds for this vulnerability.

CVSS v3
7.5
EG Score
9.0CRITICALhigh confidence
EG Risk
82
EG Risk 82/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation84% × 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 or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
84%
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 (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
84% 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 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 or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 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 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

December 15, 2023

Last Modified

June 17, 2026

Advisory Details (3)

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

Loading...

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

Solr search discloses password hashes of all users · Advisory · xwiki/xwiki-platform · GitHub

https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-p6cp-6r35-32mh
GitHub commit Patch Available

commit 3e5272f2ef0d (xwiki/xwiki-platform)

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

https://github.com/xwiki/xwiki-platform/commit/3e5272f2ef0dff06a8f4db10afd1949b2f9e6eea

Vendor Advisories for CVE-2023-50719(1)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.xwiki.platform:xwiki-platform-search-solr-api @ 14.10.15 (fixes >= 7.2-milestone-2, < 14.10.15)—ghsa
mavenorg.xwiki.platform:xwiki-platform-search-solr-api @ 15.5.2 (fixes >= 15.0-rc-1, < 15.5.2)—ghsa
mavenorg.xwiki.platform:xwiki-platform-search-solr-api @ 15.7-rc-1 (fixes >= 15.6-rc-1, < 15.7-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-search-solr-api—
  • 7.2-milestone-2 up to 14.10.15: fixed in 14.10.15
  • 15.0-rc-1 up to 15.5.2: fixed in 15.5.2
  • 15.6-rc-1 up to 15.7-rc-1: fixed in 15.7-rc-1
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 29× 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 161 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 61 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2023/CVE-2023-50719.yaml
    Published Jun 18, 2024

    XWiki < 4.10.15 - Sensitive Information Disclosure

    Open source ↗

Related CVEs(same product + same CWE)

Same product

2 shown

Maven:org.xwiki.platform:xwiki-platform-search-solr-api

Frequently asked(5)

What is CVE-2023-50719?
CVE-2023-50719 is a critical-severity vulnerability; its CVE record was published on December 15, 2023. XWiki Platform is a generic wiki platform. Starting in 7.2-milestone-2 and prior to versions 14.10.15, 15.5.2, and 15.7-rc-1, the Solr-based search in XWiki discloses the password hashes of all users to anyone with view right on the respective user profiles. By default, all user profiles are…
When was the CVE record for CVE-2023-50719 published?
The CVE record for CVE-2023-50719 was published on December 15, 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-50719 actively exploited?
CVE-2023-50719 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 84% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-50719?
CVE-2023-50719 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2023-50719?
A fix for CVE-2023-50719 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-50719 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-50719

Explore →

Is Your Infrastructure Affected by CVE-2023-50719?

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

Book a Demo →Browse All CVEs