CVE-2023-50719 is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.xwiki.platform:xwiki-platform-search-solr-api. EPSS puts its 30-day exploitation probability at 83.5% (100th percentile). A fix is available for org.xwiki.platform:xwiki-platform-search-solr-api — see the affected versions and patch details below.
XWiki Platform Solr search discloses password hashes of all users
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-50719.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2023-50719 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.xwiki.platform:xwiki-platform-search-solr-api☕org.xwiki.platform:xwiki-platform-search-solr-api☕org.xwiki.platform:xwiki-platform-search-solr-apiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-search-solr-api | ≥ 7.2-milestone-2&&< 14.10.15 | 14.10.15org.xwiki.platform:xwiki-platform-search-solr-api:14.10.15 |
| ☕Maven | org.xwiki.platform:xwiki-platform-search-solr-api | ≥ 15.0-rc-1&&< 15.5.2 | 15.5.2org.xwiki.platform:xwiki-platform-search-solr-api:15.5.2 |
| ☕Maven | org.xwiki.platform:xwiki-platform-search-solr-api | ≥ 15.6-rc-1&&< 15.7-rc-1 | 15.7-rc-1org.xwiki.platform:xwiki-platform-search-solr-api:15.7-rc-1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-search-solr-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-search-solr-api to 14.10.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-50719 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-50719 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-50719. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect CVE-2023-50719
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2023-50719 -u https://target- Template
- XWiki < 4.10.15 - Sensitive Information Disclosure
- Severity
- high
- Impact
- Successful exploitation could lead to disclosure of the password hashes of all users.
- Remediation
- This has been patched in XWiki 14.10.15, 15.5.2 and 15.7RC1.
Template by ProjectDiscovery nuclei-templates (ritikchaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2023-50719 in your dependencies?
O3 Security finds CVE-2023-50719 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.