Skip to main content

XWiki Platform CVE-2025-52472

CRITICAL
SQL Injection (CWE-89)
2025-10-06 security-advisories@github.com
9.3
CVSS 4.0 · Vendor: github
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach REST search endpoint unauthenticated
  2. Delivery
    Craft orderField HQL injection payload
  3. Exploit
    Balance quotes across double value insertion
  4. Execution
    Execute injected HQL via Hibernate
  5. Impact
    Exfiltrate database contents time-based

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation targets the XWiki REST search API (wiki and space search, e.g. /xwiki/rest/wikis/{wiki}/search) via the orderField query parameter, which is concatenated into an HQL ORDER BY/SELECT without sanitization. Per the CVSS vector (PR:N) the endpoint is reachable unauthenticated, but in practice the attacker must be able to reach the search endpoint - most impactful where anonymous/guest users retain view and search rights. The key LIMITING factor is structural: the orderField value is injected twice into the generated query (field list and order clause), so a working payload must use single quotes to null out intervening fragments while keeping BOTH copies valid HQL - this materially raises exploitation complexity. Payloads are also database-dependent (the published PoC uses PostgreSQL-specific pg_sleep). Applies to XWiki 4.3-milestone-1 up to (but not including) 16.10.9 / 17.4.2; no workaround exists other than upgrading.

Impact

This is a genuine high-priority issue for internet-facing XWiki instances, but the raw 9.3 (CVSS 4.0) overstates ease of exploitation. The vendor vector claims AV:N/AC:L/PR:N/UI:N (unauthenticated, low complexity, full VC/VI/VA:H), yet the official description and GHSA advisory explicitly state the flaw is 'not that easy to exploit' because the orderField value is inserted TWICE in the generated HQL - once in the SELECT field list and once in the ORDER BY clause - so any payload must keep BOTH copies syntactically valid via careful quote balancing. This is a direct CVSS conflict: the vendor rates AC:L, but their own exploitation narrative is consistent with AC:H - verify complexity before treating as trivially weaponizable. EPSS is 2.37% (83rd percentile), elevated relative to the average CVE but still a low absolute probability, and the vulnerability is NOT in CISA KEV, indicating no confirmed active exploitation - consistent with a theoretically serious but operationally fiddly injection. A proof-of-concept time-based (PostgreSQL pg_sleep) payload and full request URL are published in the GHSA advisory, lowering the research barrier. Net: patch promptly on any XWiki reachable by untrusted users (especially where guests can search), but this is more 'serious bug with public PoC, exploitation constrained' than 'mass-exploited critical.'

Exploit ScenarioDerived

An unauthenticated attacker sends a crafted GET request to the XWiki REST search endpoint (e.g. /xwiki/rest/wikis/{wiki}/search) with a malicious orderField parameter containing an HQL injection that uses single quotes to neutralize the surrounding query fragments. The GHSA advisory publishes a working time-based payload using pg_sleep to prove injection, enabling boolean/time-based extraction of database contents. Because the attacker-controlled value is reflected into the query twice, the payload must remain valid in both positions, making reliable data exfiltration non-trivial but demonstrated.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.
Patch available 2.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 09, 2026

Unauthenticated HQL injection in the XWiki Platform REST search API lets remote attackers inject arbitrary Hibernate Query Language through the orderField parameter of the wiki and space search endpoints, potentially exposing or manipulating data stored behind the wiki. The flaw affects XWiki Platform from 4.3-milestone-1 up to (but not including) 16.10.9 and 17.4.2, and is also fixed in 17.5.0; the vendor advisory publishes a sample payload demonstrating the injection. This is a genuine high-priority issue for internet-facing XWiki installations, but exploitation is materially harder than the raw 9.3 CVSS 4.0 score suggests: the injected value is concatenated twice into the generated query, so a working payload must null out the intervening fragments with single quotes while keeping both copies valid HQL, and usable payloads are database-specific. No public exploit code identified at time of analysis; EPSS is 2.37% (83rd percentile).

RemediationAI

Upgrade to a fixed release - XWiki Platform 16.10.9, 17.4.2, or 17.5.0 - as the primary and vendor-recommended fix; the patches add strict asc/desc validation for the order clause and route the REST search queries through the secure QueryManager. The vendor states there is no known workaround, so any compensating control is partial: on internet-facing instances, remove anonymous/guest view and search rights so the search endpoint is not reachable unauthenticated (side effect: breaks public wikis and anonymous browsing), restrict access to /xwiki/rest/wikis/*/search at the reverse proxy or WAF and drop or rewrite requests whose orderField value is anything other than asc/desc (side effect: may block legitimate custom sorting, but XWiki only supports those two values here), and rate-limit or temporarily disable the REST search endpoints while patching. Database-side hardening should not be relied on as the fix, and network filtering alone is a stopgap. Reference the advisory at https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-gprp-h92g-gc2h, the JIRA issue at https://jira.xwiki.org/browse/XWIKI-23247, and the upstream fix commits 743ebf8696ffa55161ed2c5ecf26b09f69e6bcf1 and a45eca2af772abb7324e56d7fd2df1ac937bc445.

Affected Packages

maven org.xwiki.platform:xwiki-platform-rest-server fix: 16.10.9, 17.4.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in maven

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

XWiki's REST search resources build queries in Hibernate Query Language (HQL), Hibernate's object-oriented query language that operates on mapped entities such as com.xpn.xwiki.doc.XWikiDocument rather than raw tables. The vulnerability class is CWE-89 (SQL/HQL injection): the orderField request parameter is string-concatenated into the generated query without validation, appearing once in the SELECT field list and once in the ORDER BY clause. Because HQL still permits DBMS-specific functions, injected fragments can invoke backend functions such as PostgreSQL's pg_sleep, enabling blind data exfiltration or time-based inference. The patch introduces HqlQueryUtils.getValidQueryOrder(order, def), which whitelists only asc and desc (case-insensitive) and falls back to a default otherwise, and switches the affected REST resources (BaseSearchResult, ModificationsResourceImpl) from the standard QueryManager to the secure QueryManager, which enforces XWiki's restricted query execution rules. The provided independent assessment rates the issue CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:N/C:H/I:L/A:L, i.e. no authentication or user interaction required but high attack complexity, with high confidentiality impact and limited integrity/availability impact.

Know when Xwiki gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (github) PRIMARY 9.3 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 7.0 HIGH

Unauthenticated network REST endpoint (AV:N/PR:N) but double value insertion makes reliable injection hard (AC:H); HQL SELECT context enables broad data read (C:H) without stacked writes (I:L) and only time-based DoS (A:L).

3.1 AV:N/AC:H/PR:N/UI:N/S:N/C:H/I:L/A:L
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (github).

CVSS VectorVendor: github

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. Starting in version 4.3-milestone-1 and prior to versions 16.10.9, 17.4.2, and 17.5.0, the REST search URL is vulnerable to HQL injection via the orderField parameter. The specified value is added twice in the query, though, once in the field list for the select and once in the order clause, so it's not that easy to exploit. The part of the query between the two fields can be enclosed in single quotes to effectively remove them, but the query still needs to remain valid with the query two times in it. This has been patched in versions 17.5.0, 17.4.2, and 16.10.9. No known workarounds are available.

Executive ViewAI

Why It Matters

XWiki Platform, an enterprise collaboration and knowledge management system, is affected by a critical severity vulnerability in its REST search API that could allow remote attackers to access or manipulate sensitive wiki data. No public exploit identified at time of analysis, but the potential for data breach or integrity loss makes this a high-priority issue for organizations with internet-facing XWiki deployments. Leadership should ensure immediate mitigation steps are taken, especially given the absence of a vendor-released patch at this time.

Business Impact: High
Compensating Controls

Restrict access to the XWiki REST search API to trusted networks, disable the orderField parameter if feasible, deploy WAF rules to detect and block HQL injection patterns, and monitor logs for anomalous query activity.

Threat Intelligence Overview

EPSS Score
2.4%
Top 17% exploitable
Prevalence
Low
niche open-source enterprise wiki, limited production deployment footprint
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS 2.4%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity + public POC available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

68
Low Medium High Critical
KEV: 0
EPSS: +2
CVSS: +46
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

More in Xwiki

View all
CVE-2025-24893 CRITICAL POC
9.8 Feb 20

XWiki Platform allows unauthenticated remote code execution through the SolrSearch endpoint, enabling guests to execute

CVE-2024-21650 CRITICAL POC
10.0 Jan 08

XWiki Platform prior to specific patched versions contains a CVSS 10.0 remote code execution vulnerability through the u

CVE-2025-32969 CRITICAL POC
9.3 Apr 23

XWiki is a generic wiki platform. Rated critical severity (CVSS 9.3), this vulnerability is remotely exploitable, no aut

CVE-2023-27479 CRITICAL POC
9.9 Mar 07

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. Rated critical

CVE-2023-26055 CRITICAL POC
9.9 Mar 02

XWiki Commons are technical libraries common to several other top level XWiki projects. Rated critical severity (CVSS 9.

CVE-2024-31996 CRITICAL POC
9.8 Apr 10

XWiki Platform is a generic wiki platform. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitabl

CVE-2024-31982 CRITICAL POC
9.8 Apr 10

XWiki Platform is a generic wiki platform. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitabl

CVE-2023-46731 CRITICAL POC
9.8 Nov 06

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. Rated critical

CVE-2023-26477 CRITICAL POC
9.8 Mar 02

XWiki Platform is a generic wiki platform. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitabl

CVE-2025-49586 HIGH POC
8.8 Jun 13

A remote code execution vulnerability in XWiki (CVSS 8.8). Risk factors: public PoC available. Vendor patch is available

CVE-2025-55747 CRITICAL POC
9.3 Sep 03

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. Rated critical

CVE-2025-46558 CRITICAL POC
9.0 Apr 30

XWiki Contrib's Syntax Markdown allows importing Markdown content into wiki pages and creating wiki content in Markdown.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy