XWiki's REST APIs don't enforce any limits, leading to unavailability and OOM in large wikis
### 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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-66473US | high7.5 | — | ||
XWiki is an open-source wiki software platform. Versions 16.10.10 and below, 17.0.0-rc-1 through 17.4.3 and 17.5.0-rc-1 through 17.6.0 contain a REST API which doesn't enforce any… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/xwiki/xwiki-platformPACKAGE
- https://github.com/xwiki/xwiki-platform/commit/e3c47745195fb445b054537be86f5c01ee69558bWEB
- https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-cc84-q3v3-mhgfWEB
- https://jira.xwiki.org/browse/XWIKI-23355WEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-66473ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan