CVE-2025-66473 — xwiki-platform-rest-server
Fix: xwiki/xwiki-platform@e3c4774CVE-2025-66473 is a CWE-770 vulnerability in org.xwiki.platform:xwiki-platform-rest-server. A fix is available for org.xwiki.platform:xwiki-platform-rest-server — see the affected versions and patch details below.
XWiki's REST APIs don't enforce any limits, leading to unavailability and OOM in large wikis
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-66473.
EPSS Exploitation Probability
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.
Real-World Exposure
org.xwiki.platform:xwiki-platform-rest-server☕org.xwiki.platform:xwiki-platform-rest-server☕org.xwiki.platform:xwiki-platform-rest-serverReal-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
XWiki's REST API doesn't enforce any limits for the number of items that can be requested in a single request at the moment. Depending on the number of pages in the wiki and the memory configuration, this can lead to slowness and unavailability of the wiki. As an example, the /rest/wikis/xwiki/spaces resource returns all spaces on the wiki by default, which are basically all pages.
Patches
XWiki 17.7.0RC1, 17.4.4 and 16.10.11 introduce a configurable limit, limiting responses to 1000 items by default. Requesting larger limits leads to an error now.
Workarounds
We're not aware of any workaround, except denying access to the affected REST resources in a proxy in front of XWiki.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-rest-server | all versions | 16.10.11org.xwiki.platform:xwiki-platform-rest-server:16.10.11 |
| ☕Maven | org.xwiki.platform:xwiki-platform-rest-server | ≥ 17.0.0-rc-1&&< 17.4.4 | 17.4.4org.xwiki.platform:xwiki-platform-rest-server:17.4.4 |
| ☕Maven | org.xwiki.platform:xwiki-platform-rest-server | ≥ 17.5.0-rc-1&&< 17.7.0-rc-1 | 17.7.0-rc-1org.xwiki.platform:xwiki-platform-rest-server:17.7.0-rc-1 |
Detection & mitigation playbook
Open-source dependencyDetect
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 16.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-66473 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-66473 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-66473. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-66473 in your dependencies?
O3 Security finds CVE-2025-66473 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.