GHSA-r38m-cgpg-qj69 — xwiki-platform-oldcore
Fix: xwiki/xwiki-platform@f2ca864GHSA-r38m-cgpg-qj69 is a CWE-359 vulnerability in org.xwiki.platform:xwiki-platform-oldcore. A fix is available for org.xwiki.platform:xwiki-platform-oldcore — see the affected versions and patch details below.
XWiki leaks password hashes and other accessible password properties
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-r38m-cgpg-qj69.
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.
Real-World Exposure
org.xwiki.platform:xwiki-platform-oldcore☕org.xwiki.platform:xwiki-platform-oldcore☕org.xwiki.platform:xwiki-platform-oldcore☕org.xwiki.platform:xwiki-platform-legacy-oldcore☕org.xwiki.platform:xwiki-platform-legacy-oldcore☕org.xwiki.platform:xwiki-platform-legacy-oldcoreReal-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
Any user with edit right on a page of the wiki can create an XClass with a database list property that references a password property, for example the password hash that is stored for users. When adding an object of that XClass, the content of that password property is displayed. In practice, with a standard rights setup, this means that any user with an account on the wiki can access password hashes of all users, and possibly other password properties (with hashed or plain storage) that are on pages that the user can view.
Patches
This vulnerability has been pached in XWiki 16.4.7, 16.10.5, and 17.2.0 by disallowing the use of password properties in database list properties. Additionally, queries for email properties are disallowed, too, when email obfuscation is enabled.
Workarounds
We're not aware of any workarounds.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-oldcore | ≥ 9.8-rc-1&&< 16.4.7 | 16.4.7org.xwiki.platform:xwiki-platform-oldcore:16.4.7 |
| ☕Maven | org.xwiki.platform:xwiki-platform-oldcore | ≥ 16.5.0-rc-1&&< 16.10.5 | 16.10.5org.xwiki.platform:xwiki-platform-oldcore:16.10.5 |
| ☕Maven | org.xwiki.platform:xwiki-platform-oldcore | ≥ 17.0.0-rc-1&&< 17.2.0-rc-1 | 17.2.0-rc-1org.xwiki.platform:xwiki-platform-oldcore:17.2.0-rc-1 |
| ☕Maven | org.xwiki.platform:xwiki-platform-legacy-oldcore | ≥ 9.8-rc-1&&< 16.4.7 | 16.4.7org.xwiki.platform:xwiki-platform-legacy-oldcore:16.4.7 |
| ☕Maven | org.xwiki.platform:xwiki-platform-legacy-oldcore | ≥ 16.5.0-rc-1&&< 16.10.5 | 16.10.5org.xwiki.platform:xwiki-platform-legacy-oldcore:16.10.5 |
| ☕Maven | org.xwiki.platform:xwiki-platform-legacy-oldcore | ≥ 17.0.0-rc-1&&< 17.2.0-rc-1 | 17.2.0-rc-1org.xwiki.platform:xwiki-platform-legacy-oldcore:17.2.0-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-oldcore, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-oldcore to 16.4.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r38m-cgpg-qj69 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 GHSA-r38m-cgpg-qj69 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-r38m-cgpg-qj69. 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-r38m-cgpg-qj69 in your dependencies?
O3 Security finds GHSA-r38m-cgpg-qj69 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.