CVE-2025-48063

XWiki Platform Security Authorization Bridge allows users with just edit right can enforce required rights with programming right

Workarounds

We're not aware of any workarounds except for upgrading.

In XWiki 16.10.0, required rights were introduced as a way to limit which rights a document can have. Part of the security model of required rights is that a user who doesn't have a right also cannot define that right as required right. That way, users who are editing documents on which required rights are enforced can be sure that they're not giving a right to a script or object that it didn't have before. A bug in the implementation of the enforcement of this rule means that in fact, it was possible for any user with edit right on a document to set programming right as required right. If then a user with programming right edited that document, the content of that document would gain programming right, allowing remote code execution. This thereby defeats most of the security benefits of required rights. As XWiki still performs the required rights analysis when a user edits a page even when required rights are enforced, the user with programming right would still be warned about the dangerous content unless the attacker managed to bypass this check (see, e.g., https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-c32m-27pj-4xcj). Note also that none of the affected versions include a UI for enabling the enforcing of required rights so it seems unlikely that anybody relied on them for security in the affected versions. As this vulnerability provides no additional attack surface unless all documents in the wiki enforce required rights, we consider the impact of this attack to be low even though gaining programming right could have a high impact.

Kodem intelligence

Already deployed Kodem?

This vulnerability has been patched in XWiki 16.10.4 and 17.1.0RC1.

1. What is CVE-2025-48063? CVE-2025-48063 is a medium-severity security vulnerability in org.xwiki.platform:xwiki-platform-security-authorization-bridge (maven), affecting versions >= 16.10.0-rc-1, < 16.10.4. It is fixed in 16.10.4, 17.1.0-rc-1.
2. Which versions of org.xwiki.platform:xwiki-platform-security-authorization-bridge are affected by CVE-2025-48063? org.xwiki.platform:xwiki-platform-security-authorization-bridge (maven) versions >= 16.10.0-rc-1, < 16.10.4 is affected.
3. Is there a fix for CVE-2025-48063? Yes. CVE-2025-48063 is fixed in 16.10.4, 17.1.0-rc-1. Upgrade to this version or later.
4. Is CVE-2025-48063 exploitable, and should I be worried? Whether CVE-2025-48063 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
5. What actually determines whether CVE-2025-48063 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.
6. How do I fix CVE-2025-48063?
   • Upgrade org.xwiki.platform:xwiki-platform-security-authorization-bridge to 16.10.4 or later
   • Upgrade org.xwiki.platform:xwiki-platform-security-authorization-bridge to 17.1.0-rc-1 or later