# CVE-2026-48048: XWiki Platform's Livetable results still allow reconstructing password hashes using 768 requests > Attackers can reconstruct user password hashes via Livetable results, exposing sensitive credentials in XWiki Platform. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Aug 2026 - **Updated:** 10 Aug 2026 - **Also known as:** GHSA-rh28-mqj4-8x59 ## What is CVE-2026-48048? CVE-2026-48048 is a high-severity vulnerability in xwiki-platform, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description XWiki Platform is a generic wiki platform. XWiki discovered that the patch for GHSA-5cf8-vrr8-8hjm was insufficient. Starting with version 6.2.1 and prior to versions 18.0.0RC1, 17.10.13, 17.4.9 and 16.10.17, with slightly modified parameters to the `LiveTableResults`, it is still possible to discover password hashes one bit at a time, so with 768 requests, the full password salt and hash can be retrieved of a user. The check for password (and email properties) has been adjusted in XWiki 18.0.0RC1, 17.10.13, 17.4.9 and 16.10.17. As a workaround, the patch can be applied manually to the wiki page `XWiki.LiveTableResultsMacros`. Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor) ## Which versions are affected by CVE-2026-48048? 6 open source packages ship an affected version, including org.xwiki.platform:xwiki-platform-livetable-ui. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.xwiki.platform:xwiki-platform-livetable-ui` | Maven | From 17.0.0-rc-1 | 17.4.9 | | `org.xwiki.platform:xwiki-platform-livetable-ui` | Maven | From 17.0.0-rc-1 | 17.4.9 | | `org.xwiki.platform:xwiki-platform-livetable-ui` | Maven | From 17.5.0-rc-1 | 17.10.3 | | `org.xwiki.platform:xwiki-platform-livetable-ui` | Maven | From 17.5.0-rc-1 | 17.10.3 | | `org.xwiki.platform:xwiki-platform-livetable-ui` | Maven | From 6.2.1 | 16.10.17 | | `org.xwiki.platform:xwiki-platform-livetable-ui` | Maven | From 6.2.1 | 16.10.17 | ## How do I fix CVE-2026-48048? Upgrade org.xwiki.platform:xwiki-platform-livetable-ui to a fixed version for your release line: 17.4.9, 17.10.3 or 16.10.17. ## Is CVE-2026-48048 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48048 exists. Public exploit code: - XWiki Platform - Password Hash Disclosure (nuclei): http/cves/2026/CVE-2026-48048.yaml ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-48048 and fix it if it is affected. What it is: CVE-2026-48048 is a high-severity vulnerability in xwiki-platform, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48048 exists. Affected packages and fixed versions: - org.xwiki.platform:xwiki-platform-livetable-ui (Maven): affected from 17.0.0-rc-1; fixed in 17.4.9 - org.xwiki.platform:xwiki-platform-livetable-ui (Maven): affected from 17.0.0-rc-1; fixed in 17.4.9 - org.xwiki.platform:xwiki-platform-livetable-ui (Maven): affected from 17.5.0-rc-1; fixed in 17.10.3 - org.xwiki.platform:xwiki-platform-livetable-ui (Maven): affected from 17.5.0-rc-1; fixed in 17.10.3 - org.xwiki.platform:xwiki-platform-livetable-ui (Maven): affected from 6.2.1; fixed in 16.10.17 - org.xwiki.platform:xwiki-platform-livetable-ui (Maven): affected from 6.2.1; fixed in 16.10.17 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-48048/ (Markdown: https://insights.sbomify.com/CVE-2026-48048/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48048 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48048 - OSV: https://osv.dev/vulnerability/CVE-2026-48048 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-48048/ Summaries are generated and may contain mistakes; the official description above is the record.