Summary
XWiki uses the wrong wiki reference in AuthorizationManager
Workarounds
There's no workaround.
References
- JIRA ticket: https://jira.xwiki.org/browse/XWIKI-22640
- Commit of the fix: https://github.com/xwiki/xwiki-platform/commit/5f98bde87288326cf5787604e2bb87836875ed0e
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
Impact
It's possible for an user to get access to private information through the REST API - but could also be through another API - when a sub wiki is using "Prevent unregistered users to view pages". The vulnerability only affects subwikis, and it only concerns specific right options such as "Prevent unregistered users to view pages". or "Prevent unregistered users to edit pages".
It's possible to detect the vulnerability by enabling "Prevent unregistered users to view pages" and then trying to access a page through the REST API without using any credentials.
The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.
CVE-2025-29924 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (15.10.14, 16.4.6, 16.10.0-rc-1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The vulnerability has been patched in XWiki 15.10.14, 16.4.6 and 16.10.0RC1.
Frequently Asked Questions
- What is CVE-2025-29924? CVE-2025-29924 is a high-severity improper privilege management vulnerability in org.xwiki.platform:xwiki-platform-security-authorization-api (maven), affecting versions >= 6.1-rc-1, < 15.10.14. It is fixed in 15.10.14, 16.4.6, 16.10.0-rc-1. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
- How severe is CVE-2025-29924? CVE-2025-29924 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.xwiki.platform:xwiki-platform-security-authorization-api are affected by CVE-2025-29924? org.xwiki.platform:xwiki-platform-security-authorization-api (maven) versions >= 6.1-rc-1, < 15.10.14 is affected.
- Is there a fix for CVE-2025-29924? Yes. CVE-2025-29924 is fixed in 15.10.14, 16.4.6, 16.10.0-rc-1. Upgrade to this version or later.
- Is CVE-2025-29924 exploitable, and should I be worried? Whether CVE-2025-29924 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-29924 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-29924?
- Upgrade
org.xwiki.platform:xwiki-platform-security-authorization-apito 15.10.14 or later - Upgrade
org.xwiki.platform:xwiki-platform-security-authorization-apito 16.4.6 or later - Upgrade
org.xwiki.platform:xwiki-platform-security-authorization-apito 16.10.0-rc-1 or later
- Upgrade