CVE-2026-61689

8.8High

Published 17 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

8.8CVSS

High

0CVSS v4.010

Attack vector
Network
Complexity
Low
Privileges
None
User action
None
Impact
High impact on confidentiality
Weakness
CWE-943

What an attacker gets

Unauthenticated attackers can extract sensitive database contents, including password hashes, via the REST API. They do not need any prior access or user interaction to perform this attack.

Root cause

The REST endpoint allows HQL query injection by bypassing the SELECT-column whitelist.

Affected versions

XWiki Platform 4.3-milestone-1 through 16.10.17, 17.10.4, and 18.1.x

CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Fix & remediation

Upgrade to XWiki 16.10.18, 17.10.5, or 18.2.0. If you cannot patch immediately, disable HQL and XWQL REST queries in your XWiki configuration.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD description

XWiki Platform is a generic wiki platform. From 4.3-milestone-1 until 16.10.18, 17.10.5, and 18.2.0, the /rest/wikis/{wikiName}/query REST endpoint permits HQL query construction that can combine blind conditions with FROM-clause injection to join BaseObject and StringProperty, bypassing the SELECT-column whitelist. An unauthenticated attacker can recover database values from inaccessible pages, including salted SHA1 password hashes and passwords stored in configuration properties. It should be assumed that, with more complex techniques, this can work even when the attacker cannot read any wiki page. A typical password hash may require roughly 800 requests, and expensive injected queries can also degrade availability. The issue is remediated by disabling HQL and XWQL REST queries by default. This issue is fixed in versions 16.10.18, 17.10.5, and 18.2.0.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-61689