Summary
Workarounds
We're not aware of any workarounds.
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.
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 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.
Frequently Asked Questions
- What is CVE-2025-54124? CVE-2025-54124 is a high-severity security vulnerability in org.xwiki.platform:xwiki-platform-oldcore (maven), affecting versions >= 9.8-rc-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-54124?
org.xwiki.platform:xwiki-platform-oldcore(maven) (versions >= 9.8-rc-1, < 16.4.7)org.xwiki.platform:xwiki-platform-legacy-oldcore(maven) (versions >= 9.8-rc-1, < 16.4.7)
- Is there a fix for CVE-2025-54124? Yes. CVE-2025-54124 is fixed in 16.4.7, 16.10.5, 17.2.0-rc-1. Upgrade to this version or later.
- Is CVE-2025-54124 exploitable, and should I be worried? Whether CVE-2025-54124 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-54124 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-54124?
- 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