# CVE-2025-52472: XWiki Platform vulnerable to HQL injection via wiki and space search REST API

> Attackers can inject HQL queries via the REST search API to read or modify data in XWiki Platform.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2025
- **Updated:** 6 Oct 2025
- **Also known as:** GHSA-gprp-h92g-gc2h

## What is CVE-2025-52472?

CVE-2025-52472 is a critical SQL injection vulnerability in xwiki-platform, published on 6 Oct 2025. 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 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-52472?

4 open source packages ship an affected version, including org.xwiki.platform:xwiki-platform-rest-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.xwiki.platform:xwiki-platform-rest-server` | Maven | From 17.0.0-rc-1 | 17.4.2 |
| `org.xwiki.platform:xwiki-platform-rest-server` | Maven | From 17.0.0-rc-1 | 17.4.2 |
| `org.xwiki.platform:xwiki-platform-rest-server` | Maven | From 4.3-milestone-1 | 16.10.9 |
| `org.xwiki.platform:xwiki-platform-rest-server` | Maven | From 4.3-milestone-1 | 16.10.9 |

## How do I fix CVE-2025-52472?

Upgrade org.xwiki.platform:xwiki-platform-rest-server to a fixed version for your release line: 17.4.2 or 16.10.9.

## Is CVE-2025-52472 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52472 exists.

Public exploit code:

- XWiki - HQL Injection (nuclei): http/cves/2025/CVE-2025-52472.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52472 and fix it if it is affected.

What it is: CVE-2025-52472 is a critical SQL injection vulnerability in xwiki-platform, published on 6 Oct 2025. 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-2025-52472 exists.

Affected packages and fixed versions:
- org.xwiki.platform:xwiki-platform-rest-server (Maven): affected from 17.0.0-rc-1; fixed in 17.4.2
- org.xwiki.platform:xwiki-platform-rest-server (Maven): affected from 17.0.0-rc-1; fixed in 17.4.2
- org.xwiki.platform:xwiki-platform-rest-server (Maven): affected from 4.3-milestone-1; fixed in 16.10.9
- org.xwiki.platform:xwiki-platform-rest-server (Maven): affected from 4.3-milestone-1; fixed in 16.10.9

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-2025-52472/ (Markdown: https://insights.sbomify.com/CVE-2025-52472/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52472
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52472
- OSV: https://osv.dev/vulnerability/CVE-2025-52472

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52472/
Summaries are generated and may contain mistakes; the official description above is the record.
