Summary
Solr search discloses password hashes of all users
Workarounds
We're not aware of any workarounds apart from upgrading to a fixed version.
References
Impact
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. To reproduce, it is sufficient to search for propertyvalue:?* AND reference:*.password and then deselect the "Document" property under "Result type" in the "Refine your search" widget at the right of the search results. If this displays any passwords or password hashes, the installation is vulnerable.
By default, passwords in XWiki are salted and hashed with SHA-512. On XWiki versions affected by CVE-2022-41933, passwords are stored in plain text if they have been set using the password reset feature. This might affect XWiki installations that are using an external authentication mechanism such that passwords aren't stored in the wiki.
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.
CVE-2023-50719 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (14.10.15, 15.5.2, 15.7-rc-1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This has been patched in XWiki 14.10.15, 15.5.2 and 15.7RC1. This vulnerability has been patched as part of patching GHSA-2grh-gr37-2283, the part of the fix that changes the indexing of single properties to use the same code as the main document for getting the property's value fixes this vulnerability.
Frequently Asked Questions
- What is CVE-2023-50719? CVE-2023-50719 is a high-severity security vulnerability in org.xwiki.platform:xwiki-platform-search-solr-api (maven), affecting versions >= 7.2-milestone-2, < 14.10.15. It is fixed in 14.10.15, 15.5.2, 15.7-rc-1.
- How severe is CVE-2023-50719? CVE-2023-50719 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.xwiki.platform:xwiki-platform-search-solr-api are affected by CVE-2023-50719? org.xwiki.platform:xwiki-platform-search-solr-api (maven) versions >= 7.2-milestone-2, < 14.10.15 is affected.
- Is there a fix for CVE-2023-50719? Yes. CVE-2023-50719 is fixed in 14.10.15, 15.5.2, 15.7-rc-1. Upgrade to this version or later.
- Is CVE-2023-50719 exploitable, and should I be worried? Whether CVE-2023-50719 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2023-50719 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2023-50719?
- Upgrade
org.xwiki.platform:xwiki-platform-search-solr-apito 14.10.15 or later - Upgrade
org.xwiki.platform:xwiki-platform-search-solr-apito 15.5.2 or later - Upgrade
org.xwiki.platform:xwiki-platform-search-solr-apito 15.7-rc-1 or later
- Upgrade