How severe is CVE-2025-32969?

No CVSS score has been assigned to CVE-2025-32969 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-32969?

CVE-2025-32969 affects the following packages: org.xwiki.platform:xwiki-platform-rest-server (Maven), org.xwiki.platform:xwiki-platform-rest-server (Maven), org.xwiki.platform:xwiki-platform-rest-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-32969?

Update org.xwiki.platform:xwiki-platform-rest-server to 15.10.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32969 is resolved across your whole dependency graph.

How do I detect CVE-2025-32969 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-rest-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-32969 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2025-32969 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-32969 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-32969?

CVE-2025-32969 has an EPSS (Exploit Prediction Scoring System) score of 80.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2025-32969?

CVE-2025-32969 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2025-32969?

A Nuclei detection template exists for CVE-2025-32969, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2025-32969 published, and has it been updated?

CVE-2025-32969 was published on April 23, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2025-32969 — xwiki-platform-rest-server

Fix: xwiki/xwiki-platform@5c11a87

CVE-2025-32969 is a SQL Injection vulnerability in org.xwiki.platform:xwiki-platform-rest-server. EPSS puts its 30-day exploitation probability at 80.0% (100th percentile). A fix is available for org.xwiki.platform:xwiki-platform-rest-server — see the affected versions and patch details below.

org.xwiki.platform:xwiki-platform-rest-server allows SQL injection in query endpoint of REST API

Also known asGHSA-f69v-xrj8-rhxf

Published

Apr 23, 2025

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-32969.

EPSS Exploitation Probability

via FIRST.org ↗

80.0%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

☕org.xwiki.platform:xwiki-platform-rest-server☕org.xwiki.platform:xwiki-platform-rest-server☕org.xwiki.platform:xwiki-platform-rest-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

It is possible for a remote unauthenticated user to escape from the HQL execution context and perform a blind SQL injection to execute arbitrary SQL statements on the database backend, including when "Prevent unregistered users from viewing pages, regardless of the page rights" and "Prevent unregistered users from editing pages, regardless of the page rights" options are enabled.

Depending on the used database backend, the attacker may be able to not only obtain confidential information such as password hashes from the database, but also execute UPDATE/INSERT/DELETE queries.

The vulnerability may be tested in a default installation of XWIki Standard Flavor, including using the official Docker containers.

An example query, which leads to SQL injection with MySQL/MariaDB backend is shown below:

time curl "http://127.0.0.1:8080/rest/wikis/xwiki/query?q=where%20doc.name=length('a')*org.apache.logging.log4j.util.Chars.SPACE%20or%201%3C%3E%271%5C%27%27%20union%20select%201,2,3,sleep(10)%20%23%27&type=hql&distinct=0"

When executed, the response from the server will come after a delay of 10 extra seconds, indicating successful execution of the injected SQL statement.

An example of a query for the PostgreSQL database backend is shown below:

curl "https://127.0.0.1:8080/rest/wikis/xwiki/query?q=where%20%24%24='%24%24=concat(%20chr(%2061%20),(chr(%2039%20))%20)%20;select%201%20--%20comment'&type=hql&distinct=0"

Both requests employ database backend dependent techniques of breaking out of HQL query context, described, for example, here: https://www.sonarsource.com/blog/exploiting-hibernate-injections.

Patches

This has been patched in 16.10.1, 16.4.6 and 15.10.16.

Workarounds

There is no known workaround, other than upgrading XWiki.

References

https://jira.xwiki.org/browse/XWIKI-22691

For more information

If you have any questions or comments about this advisory:

Open an issue in Jira XWiki.org
Email us at Security Mailing List

Attribution

Sergey Anufrienko from Kaspersky ICS-CERT vulnerability research team reported this vulnerability.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-rest-server`	≥ 1.8&&< 15.10.16	15.10.16`org.xwiki.platform:xwiki-platform-rest-server:15.10.16`
☕Maven	`org.xwiki.platform:xwiki-platform-rest-server`	≥ 16.0.0-rc-1&&< 16.4.6	16.4.6`org.xwiki.platform:xwiki-platform-rest-server:16.4.6`
☕Maven	`org.xwiki.platform:xwiki-platform-rest-server`	≥ 16.5.0-rc-1&&< 16.10.1	16.10.1`org.xwiki.platform:xwiki-platform-rest-server:16.10.1`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 16.5.0 && < 16.10.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-rest-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-rest-server to 15.10.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32969 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

How to detect CVE-2025-32969

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2025-32969 -u https://target

Template: XWiki REST API Query - SQL Injection
Severity: critical
Impact: Unauthenticated attackers can execute arbitrary SQL queries through the REST API query endpoint, potentially leading to complete database compromise and data exfiltration.
Remediation: Upgrade to the latest XWiki version that properly sanitizes HQL query parameters in the REST API.

Template by ProjectDiscovery nuclei-templates (ritikchaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Impact It is possible for a remote unauthenticated user to escape from the HQL execution context and perform a blind SQL injection to execute arbitrary SQL statements on the database backend, including when "Prevent unregistered users from viewing pages, regardless of the page rights" and "Prevent unregistered users from editing pages, regardless of the page rights" options are enabled. Depending on the used database backend, the attacker may be able to not only obtain confidential information such as password hashes from the database, but also execute UPDATE/INSERT/DELETE queries. The

O3 Security · Impact-Aware SCA

Is CVE-2025-32969 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works