CVE-2024-31464

XWiki Platform: Password hash might be leaked by diff once the xobject holding them is deleted

MEDIUM
4.9
CVSS Score
Published: April 10, 2024 at 06:14 PM UTC
Updated: June 17, 2026 at 07:28 AM UTC
1 product affected across 1 vendorXwiki

Using xwiki-platform by xwiki?

Get instant alerts when new vulnerabilities affect xwiki-platform - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.9
Exploit prediction
EPSS 0.4%
SSVC
PoC

Description

XWiki Platform is a generic wiki platform. Starting in version 5.0-rc-1 and prior to versions 14.10.19, 15.5.4, and 15.9-rc-1, 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. 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. a diff, to ensure it's not coming from a password field. As another mitigation, 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). There is not much workaround possible for a privileged user other than upgrading XWiki.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 14.10.19v < 15.5.4v < 15.9-rc-115.0 ≤ v < 15.5.415.0-rc-1 ≤ v < 15.5.415.6 ≤ v < 15.915.6-rc-1 ≤ v < 15.9-rc-15.0 ≤ v < 14.10.195.0-rc-1 ≤ v < 14.10.1915.0-rc-115.6-rc-15.0-rc-1
Affected range stops below 14.10.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 15.5.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 15.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 15.9-rc-1, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-200CWE-916

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card