GHSA-x7wv-5qg4-vmr6 is a critical-severity (CVSS 9) CWE-862 vulnerability in org.xwiki.platform:xwiki-platform-component-wiki. A fix is available for org.xwiki.platform:xwiki-platform-component-wiki — see the affected versions and patch details below.
org.xwiki.platform:xwiki-platform-component-wiki provides no warning when granting XWiki.ComponentClass programming right
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-x7wv-5qg4-vmr6.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-x7wv-5qg4-vmr6 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.xwiki.platform:xwiki-platform-component-wiki☕org.xwiki.platform:xwiki-platform-component-wiki☕org.xwiki.platform:xwiki-platform-component-wikiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Patches
This problem has been patched in XWiki 15.10.2, 16.4.3, and 16.8.0 RC1.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-component-wiki | ≥ 15.9-rc-1&&< 15.10.12 | 15.10.12org.xwiki.platform:xwiki-platform-component-wiki:15.10.12 |
| ☕Maven | org.xwiki.platform:xwiki-platform-component-wiki | ≥ 16.0.0-rc-1&&< 16.4.3 | 16.4.3org.xwiki.platform:xwiki-platform-component-wiki:16.4.3 |
| ☕Maven | org.xwiki.platform:xwiki-platform-component-wiki | ≥ 16.5.0-rc-1&&< 16.8.0-rc-1 | 16.8.0-rc-1org.xwiki.platform:xwiki-platform-component-wiki:16.8.0-rc-1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-component-wiki, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-component-wiki to 15.10.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x7wv-5qg4-vmr6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-x7wv-5qg4-vmr6 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-x7wv-5qg4-vmr6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-x7wv-5qg4-vmr6 in your dependencies?
O3 Security finds GHSA-x7wv-5qg4-vmr6 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.