Skip to content

← Public intelligence

Maven package

org.xwiki.platform:xwiki-platform-security-authorization-bridge

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.8MavenPublished

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

    CVE-2025-48063 · GHSA-rhfv-688c-p6hp

    Affected
    • Maven org.xwiki.platform:xwiki-platform-security-authorization-bridge >= 16.10.0-rc-1, < 16.10.4; >= 17.0.0-rc-1, < 17.1.0-rc-1
    Fixed in
    17.1.0-rc-116.10.4· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 17.1.0-rc-1 (pre-release) or 16.10.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →