GHSA-57q2-6cp4-9mq3 — xwiki-platform-oldcore
Fix: xwiki/xwiki-platform@742ee34GHSA-57q2-6cp4-9mq3 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 exposes passwords and emails stored in fields not named password/email in xml.vm
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.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for GHSA-57q2-6cp4-9mq3.
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
The XML export of a page in XWiki that can be triggered by any user with view rights on a page by appending ?xpage=xml to the URL includes password and email properties stored on a document that aren't named password or email. This allows any user to obtain the salted and hashed user account validation or password reset token. As those tokens are randomly generated strings, the immediate impact of this should be low. The user's password and email itself aren't exposed as those fields are named password and email and thus aren't affected. However, depending on how the wiki is used, there could be extensions or custom code that store passwords in plain text in such password properties that would be exposed by this vulnerability.
Patches
This vulnerability has been fixed by completely removing the output of password and email fields in this XML export in versions 17.2.0 RC1, 16.10.5 and 16.4.7.
Workarounds
If this XML export isn't needed, the file templates/xml.vm in the deployed WAR can be deleted. There isn't any feature in XWiki itself that depends on this XML export.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-oldcore | ≥ 1.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 | ≥ 1.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-57q2-6cp4-9mq3 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-57q2-6cp4-9mq3 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-57q2-6cp4-9mq3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect GHSA-57q2-6cp4-9mq3
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-57q2-6cp4-9mq3 -u https://target- Template
- XWiki XML View - Sensitive Information Exposure
- Severity
- high
- Impact
- Unauthenticated attackers can access sensitive information including passwords and email addresses stored in custom user profile fields through the XML view functionality.
- Remediation
- Upgrade XWiki to the latest version that properly protects sensitive custom fields in XML view outputs.
Template by ProjectDiscovery nuclei-templates (ritikchaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is GHSA-57q2-6cp4-9mq3 in your dependencies?
O3 Security finds GHSA-57q2-6cp4-9mq3 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.