CVE-2025-48063: XWiki Platform Security Authorization Bridge allows users with just edit right can enforce required rights with programming right

Published May 21, 2025
·
Updated

Impact 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.

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

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

Other sources

XWiki is a generic wiki platform. 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. 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. This vulnerability has been patched in XWiki 16.10.4 and 17.1.0RC1. No known workarounds are available except for upgrading.

MITRE

Affected Software

7 affected componentsFixes available
XWiki XWiki Platform<16.10.4
XWiki XWiki Platform>=16.10.0<16.10.4
maven/org.xwiki.platform:xwiki-platform-security-authorization-bridge>=17.0.0-rc-1<17.1.0-rc-1
17.1.0-rc-1
maven/org.xwiki.platform:xwiki-platform-security-authorization-bridge>=16.10.0-rc-1<16.10.4
16.10.4
XWiki xwiki>=16.10.0<16.10.4
XWiki xwiki=17.0.0
XWiki xwiki=17.0.0-rc1

Event History

May 21, 2025
CVE Published
via MITRE·05:38 PM
Data Sourced
via MITRE·05:38 PM
DescriptionWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
RemedyAffected Software
Advisory Published
via GitHub·06:26 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-48063?

CVE-2025-48063 is classified as a medium severity vulnerability.

2

How do I fix CVE-2025-48063?

To fix CVE-2025-48063, upgrade XWiki Platform to version 16.10.5 or later.

3

What versions of XWiki are affected by CVE-2025-48063?

XWiki versions 16.10.0 through 16.10.4 are affected by CVE-2025-48063.

4

What is the nature of the vulnerability in CVE-2025-48063?

CVE-2025-48063 involves improper handling of required rights, allowing unauthorized users to influence access controls.

5

Is there a workaround for CVE-2025-48063 until I can update?

Currently, there are no specific workarounds for CVE-2025-48063, so updating is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203