Skip to main content
Menu
CVEs

CVE

XWiki Platform: HQL injection in search allows unauthenticated database extraction including password hashes

CVE-2026-61689EUVD-2026-127801

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

8.8HighCNA
Exploited
No known exploitation
Fix
Fixed in 16.10.18, 17.10.5, 18.2.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 16.10.18, 17.10.5, 18.2.0.

Published
Last modified
Reference
Last checked
26/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

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.

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.8/10CVSS 8.8
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 16.10.18, 17.10.5, 18.2.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-61689 (XWiki Platform: HQL injection in search allows unauthenticated database extraction including password hashes), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-61689 (entry last updated 2026-11-17):
Affected:
- xwiki xwiki-platform: from 4.3-milestone-1, fixed in 16.10.18; from 17.0.0-rc-1, fixed in 17.10.5; from 18.0.0-rc-1, fixed in 18.2.0
Fixed versions: 16.10.18, 17.10.5, 18.2.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-61689 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-61689 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-jmmc-wjpc-pg34
- https://github.com/xwiki/xwiki-platform/commit/4d6a2cd9cd049d0c31823ce47bff0a95667967e3
- https://github.com/xwiki/xwiki-platform/commit/62b034daceead8e292244d6c9e651c0ee8b1354c
- https://github.com/xwiki/xwiki-platform/commit/ae540bc3def0d4a30210eb9bead4e559984b4462
- https://github.com/xwiki/xwiki-platform/commit/b63d383f2e2a41826c21a76d678b9b0e1ab0ce52
- https://github.com/xwiki/xwiki-platform/releases/tag/xwiki-platform-16.10.18
- https://github.com/xwiki/xwiki-platform/releases/tag/xwiki-platform-17.10.5
- https://github.com/xwiki/xwiki-platform/releases/tag/xwiki-platform-18.2.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-61689
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-61689"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • xwiki xwiki-platform

    From 4.3-milestone-1 · fixed in 16.10.18; From 17.0.0-rc-1 · fixed in 17.10.5; From 18.0.0-rc-1 · fixed in 18.2.0

Evidence 10

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 7

  1. Repository
  2. Repository
  3. Repository
  4. Repository
  5. Repository
  6. Repository
  7. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-61689

Is CVE-2026-61689 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-61689?

xwiki-platform: from 4.3-milestone-1 before 16.10.18; from 17.0.0-rc-1 before 17.10.5; from 18.0.0-rc-1 before 18.2.0.Source: cve.now feed data

How do I fix CVE-2026-61689?

Upgrade to a fixed version: 16.10.18, 17.10.5, 18.2.0.Source: cve.now feed data

More CVEs