Summary
XWiki Platform: Password hash might be leaked by diff once the xobject holding them is deleted
Workarounds
Admins should ensure that the user pages are properly protected: the edit right shouldn't be allowed for other users than Admin and owner of the profile (which is the default right).
Now there's not much workaround possible for a privileged user other than upgrading XWiki.
References
- JIRA ticket: https://jira.xwiki.org/browse/XWIKI-19948
- Commit: https://github.com/xwiki/xwiki-platform/commit/f1eaec1e512220fabd970d053c627e435a1652cf
For more information
If you have any questions or comments about this advisory:
- Open an issue in Jira XWiki.org
- Email us at Security Mailing List
Impact
It is possible to access the hash of a password by using the diff feature of the history whenever the object storing the password is deleted. Using that vulnerability it's possible for an attacker to have access to the hash password of a user if they have rights to edit the users' page.
Now with the default right scheme in XWiki this vulnerability is normally prevented on user profiles, except by users with Admin rights. Note that this vulnerability also impacts any extensions that might use passwords stored in xobjects: for those usecases it depends on the right of those pages.
There is currently no way to be 100% sure that this vulnerability has been exploited, as an attacker with enough privilege could have deleted the revision where the xobject was deleted after rolling-back the deletion. But again, this operation requires high privileges on the target page (Admin right). A page with a user password xobject which have in its history a revision where the object has been deleted should be considered at risk and the password should be changed there.
CVE-2024-31464 has a CVSS score of 6.8 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (14.10.19, 15.5.4, 15.9-rc-1); upgrading removes the vulnerable code path.
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.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The vulnerability has been patched in XWiki 14.10.19, 15.5.4 and 15.9-rc-1 by performing a better check before dislaying data of a diff, to ensure it's not coming from a password field.
Frequently Asked Questions
- What is CVE-2024-31464? CVE-2024-31464 is a medium-severity security vulnerability in org.xwiki.platform:xwiki-platform-oldcore (maven), affecting versions >= 5.0-rc-1, < 14.10.19. It is fixed in 14.10.19, 15.5.4, 15.9-rc-1.
- How severe is CVE-2024-31464? CVE-2024-31464 has a CVSS score of 6.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.xwiki.platform:xwiki-platform-oldcore are affected by CVE-2024-31464? org.xwiki.platform:xwiki-platform-oldcore (maven) versions >= 5.0-rc-1, < 14.10.19 is affected.
- Is there a fix for CVE-2024-31464? Yes. CVE-2024-31464 is fixed in 14.10.19, 15.5.4, 15.9-rc-1. Upgrade to this version or later.
- Is CVE-2024-31464 exploitable, and should I be worried? Whether CVE-2024-31464 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-2024-31464 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-2024-31464?
- Upgrade
org.xwiki.platform:xwiki-platform-oldcoreto 14.10.19 or later - Upgrade
org.xwiki.platform:xwiki-platform-oldcoreto 15.5.4 or later - Upgrade
org.xwiki.platform:xwiki-platform-oldcoreto 15.9-rc-1 or later
- Upgrade