Summary
Workarounds
We're not aware of any workarounds apart from not editing pages that might have been edited by untrusted users as a user with programming rights, e.g., by using separate user accounts for admin and non-admin tasks.
Impact
When a user with programming right edits a document in XWiki that was last edited by a user without programming right and contains an XWiki.ComponentClass, there is no warning that this will grant programming right to this object. An attacker who created such a malicious object could use this to gain programming right on the wiki. For this, the attacker needs to have edit right on at least one page to place this object and then get an admin user to edit that document.
To reproduce the problem, as a user without programming right, add an object of type XWiki.ComponentClass to any page and then edit the page as a user with programming right. There should be warning displayed, if not, the XWiki installation is vulnerable.
While such a warning didn't exist in any version of XWiki, only in XWiki 15.9 RC1 these kinds of warnings have been introduced which is why this is considered the first version that has this vulnerability. Before that, the advice was to be careful when editing pages edited by untrusted users.
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
CVE-2025-32973 has a CVSS score of 9.0 (Critical). The vector is network-reachable, low privileges required, and user interaction required. 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.12, 16.4.3, 16.8.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.
Remediation advice
This problem has been patched in XWiki 15.10.2, 16.4.3, and 16.8.0 RC1.
Frequently Asked Questions
- What is CVE-2025-32973? CVE-2025-32973 is a critical-severity missing authorization vulnerability in org.xwiki.platform:xwiki-platform-component-wiki (maven), affecting versions >= 15.9-rc-1, < 15.10.12. It is fixed in 15.10.12, 16.4.3, 16.8.0-rc-1. The application does not perform an authorization check before performing a sensitive operation.
- How severe is CVE-2025-32973? CVE-2025-32973 has a CVSS score of 9.0 (Critical). 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-component-wiki are affected by CVE-2025-32973? org.xwiki.platform:xwiki-platform-component-wiki (maven) versions >= 15.9-rc-1, < 15.10.12 is affected.
- Is there a fix for CVE-2025-32973? Yes. CVE-2025-32973 is fixed in 15.10.12, 16.4.3, 16.8.0-rc-1. Upgrade to this version or later.
- Is CVE-2025-32973 exploitable, and should I be worried? Whether CVE-2025-32973 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-32973 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-32973?
- Upgrade
org.xwiki.platform:xwiki-platform-component-wikito 15.10.12 or later - Upgrade
org.xwiki.platform:xwiki-platform-component-wikito 16.4.3 or later - Upgrade
org.xwiki.platform:xwiki-platform-component-wikito 16.8.0-rc-1 or later
- Upgrade