N/A

CVSS Score

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2025-66473

CVE-2025-66473: 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.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2025-66473

CVE-2025-66473:

N/A

CVSS Score

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
org.xwiki.platform:xwiki-platform-rest-server	maven	< 16.10.11	16.10.11
org.xwiki.platform:xwiki-platform-rest-server	maven	>= 17.0.0-rc-1, < 17.4.4	17.4.4
org.xwiki.platform:xwiki-platform-rest-server	maven	>= 17.5.0-rc-1, < 17.7.0-rc-1	17.7.0-rc-1

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability lies in the absence of input validation for parameters that control the number of items returned by various REST API endpoints and other data-fetching mechanisms in XWiki. The parameters, typically named 'number' or 'limit', were passed directly to database queries or in-memory processing loops. An attacker could specify a very large or negative value for this parameter, causing the server to attempt to fetch and process an enormous number of records. This would lead to excessive CPU and memory consumption, resulting in an OutOfMemoryError or a denial of service (DoS), making the wiki unresponsive.

The patch addresses this by introducing a centralized validation method, validateAndGetLimit(Integer limit), in the base XWikiResource class. This method checks the provided limit against a configurable system-wide query item limit (security.queryItemsLimit). If the requested limit is missing, it defaults to the configured value. If it's invalid (e.g., negative or exceeds the maximum allowed), it throws a WebApplicationException with a 400 Bad Request status, immediately stopping the request. This new validation method is then applied across dozens of resource implementation classes, effectively mitigating the vulnerability in all affected REST endpoints. The patch also extends this protection to UI components driven by Velocity templates by introducing and using new validation macros (#validateQueryLimit, #getAndValidateQueryLimitFromRequest).

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.

N/A

-

Basic Information

Basic Information

Concerned about an active attack path?

CVE-2025-66473: XWiki's REST APIs don't enforce any limits, leading to unavailability and OOM in large wikis

Impact

Patches

Workarounds

CVE-2025-66473:

N/A

-

Basic Information

Basic Information

Is this CVE running in your environment?

Technical Details

Technical Details

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Vulnerability IntelligenceMiggo AI

Unlock WAF rules for this CVE

WAF Protection Rules

WAF Rule

Reasoning

Basic Information

Basic Information

CVE-2025-66473: XWiki's REST APIs don't enforce any limits, leading to unavailability and OOM in large wikis

Impact

Patches

Workarounds

N/A

N/A

Technical Details

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI