# XWiki Platform: Password hash might be leaked by diff once the xobject holding them is deleted Advisory record · `GHSA-v782-xr4w-3vqx` - **Identifiers:** `GHSA-v782-xr4w-3vqx` · `CVE-2024-31464` - **State:** Confirmed - **Severity:** CVSS 6.8 Medium - **Critical:** No - **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-916](https://cwe.mitre.org/data/definitions/916.html) - **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md) - **Published:** 10 Apr 2024 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 10 Apr 2024, 17:07 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.xwiki.platform:xwiki-platform-oldcore` (Maven): affected `>=5.0-rc-1, <14.10.19 || >=15.0-rc-1, <15.5.4 || >=15.6-rc-1, <15.9-rc-1`; fixed in `14.10.19`, `15.5.4`, `15.9-rc-1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > XWiki Platform's oldcore module (xwiki-platform-oldcore) is vulnerable in versions from 5.0-rc-1 up to 14.10.19, from 15.0-rc-1 up to 15.5.4, and from 15.6-rc-1 up to 15.9-rc-1. A user with edit rights on a page holding a password object can view the password hash through the history diff feature after that object has been deleted. Upgrade to 14.10.19, 15.5.4, or 15.9-rc-1. Admins should also restrict edit rights on user pages to administrators and the profile owner. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 6.8 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0038, the 32nd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:18 UTC: First seen by agentprime - 31 Oct 2026, 14:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-v782-xr4w-3vqx) ## Sources - [GitHub Advisory Database: GHSA-v782-xr4w-3vqx](https://github.com/advisories/GHSA-v782-xr4w-3vqx) - [OSV: GHSA-v782-xr4w-3vqx](https://osv.dev/vulnerability/GHSA-v782-xr4w-3vqx) - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .