Summary
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.
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.
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.
Remediation advice
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.
Frequently Asked Questions
- What is CVE-2025-54125? CVE-2025-54125 is a high-severity security vulnerability in org.xwiki.platform:xwiki-platform-oldcore (maven), affecting versions >= 1.1, < 16.4.7. It is fixed in 16.4.7, 16.10.5, 17.2.0-rc-1.
- Which packages are affected by CVE-2025-54125?
org.xwiki.platform:xwiki-platform-oldcore(maven) (versions >= 1.1, < 16.4.7)org.xwiki.platform:xwiki-platform-legacy-oldcore(maven) (versions >= 1.1, < 16.4.7)
- Is there a fix for CVE-2025-54125? Yes. CVE-2025-54125 is fixed in 16.4.7, 16.10.5, 17.2.0-rc-1. Upgrade to this version or later.
- Is CVE-2025-54125 exploitable, and should I be worried? Whether CVE-2025-54125 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-2025-54125 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-2025-54125?
- Upgrade
org.xwiki.platform:xwiki-platform-oldcoreto 16.4.7 or later - Upgrade
org.xwiki.platform:xwiki-platform-oldcoreto 16.10.5 or later - Upgrade
org.xwiki.platform:xwiki-platform-oldcoreto 17.2.0-rc-1 or later - Upgrade
org.xwiki.platform:xwiki-platform-legacy-oldcoreto 16.4.7 or later - Upgrade
org.xwiki.platform:xwiki-platform-legacy-oldcoreto 16.10.5 or later - Upgrade
org.xwiki.platform:xwiki-platform-legacy-oldcoreto 17.2.0-rc-1 or later
- Upgrade