How severe is CVE-2025-32429?

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

Which packages are affected by CVE-2025-32429?

CVE-2025-32429 affects the following packages: org.xwiki.platform:xwiki-platform-distribution-war (Maven), org.xwiki.platform:xwiki-platform-distribution-war (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-32429?

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

How do I detect CVE-2025-32429 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-distribution-war. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-32429?

O3 pinpoints whether CVE-2025-32429 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Yes. There are 2 known exploit references for CVE-2025-32429, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2025-32429 has an EPSS (Exploit Prediction Scoring System) score of 84.6%, 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.

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

A Nuclei detection template exists for CVE-2025-32429, 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-32429 published, and has it been updated?

CVE-2025-32429 was published on July 24, 2025 and was last updated on April 10, 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

CVE-2025-32429

XWiki Platform vulnerable to SQL injection through getdeleteddocuments.vm template sort parameter

Also known asGHSA-vr59-gm53-v7cq

Published

Jul 24, 2025

Updated

Apr 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

84.6%probability of exploitation in next 30 days

Very High Risk100th percentile+49.66%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

☕org.xwiki.platform:xwiki-platform-distribution-war☕org.xwiki.platform:xwiki-platform-distribution-war

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

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. In versions 9.4-rc-1 through 16.10.5 and 17.0.0-rc-1 through 17.2.2, it's possible for anyone to inject SQL using the parameter sort of the getdeleteddocuments.vm. It's injected as is as an ORDER BY value. This is fixed in versions 16.10.6 and 17.3.0-rc-1.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-distribution-war`	≥ 9.4-rc-1&&< 16.10.6	16.10.6
☕Maven	`org.xwiki.platform:xwiki-platform-distribution-war`	≥ 17.0.0-rc-1&&< 17.3.0-rc-1	17.3.0-rc-1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52384webappsmultiple

XWiki 14 - SQL Injection via getdeleteddocuments.vm

by Byte Reaper · Jul 28, 2025

Exploit-DB Source

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-distribution-war. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.xwiki.platform:xwiki-platform-distribution-war to 16.10.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32429 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-32429 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-32429. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-32429 in your dependencies?

O3 detects CVE-2025-32429 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works