GHSA-p6cp-6r35-32mh
HIGHGHSA-p6cp-6r35-32mh is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.xwiki.platform:xwiki-platform-search-solr-api. O3 Security confirms whether GHSA-p6cp-6r35-32mh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Solr search discloses password hashes of all users
Blast Radius
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
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.
Patches
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.
Workarounds
We're not aware of any workarounds apart from upgrading to a fixed version.
References
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.15 |
| ☕Maven | org.xwiki.platform:xwiki-platform-search-solr-api | ≥ 15.0-rc-1&&< 15.5.2 | 15.5.2 |
| ☕Maven | org.xwiki.platform:xwiki-platform-search-solr-api | ≥ 15.6-rc-1&&< 15.7-rc-1 | 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-p6cp-6r35-32mh 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 pinpoints whether GHSA-p6cp-6r35-32mh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-p6cp-6r35-32mh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-p6cp-6r35-32mh in your dependencies?
O3 detects GHSA-p6cp-6r35-32mh across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.