org.xwiki.platform:xwiki-platform-security-requiredrights-default required rights analysis doesn't consider TextAreas with default content typeGHSA-mvgm-3rw2-7j4r
CRITICALFix: xwiki/xwiki-platform@153dbfaGHSA-mvgm-3rw2-7j4r is a critical-severity (CVSS 9) CWE-116 vulnerability in org.xwiki.platform:xwiki-platform-security-requiredrights-default. A fix is available for org.xwiki.platform:xwiki-platform-security-requiredrights-default — see the affected versions and patch details below.
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-mvgm-3rw2-7j4r.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.xwiki.platform:xwiki-platform-security-requiredrights-default☕org.xwiki.platform:xwiki-platform-security-requiredrights-defaultReal-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 editing a page, XWiki warns since version 15.9 when there is content on the page like a script macro that would gain more rights due to the editing. This analysis doesn't consider certain kinds of properties, allowing a user to put malicious scripts in there that will be executed after a user with script, admin, or programming rights edited the page. Such a malicious script could impact the confidentiality, integrity and availability of the whole XWiki installation.
To reproduce, as a user without script right, create a class with a TextArea property, create page with an object of that class and a Velocity macro in its content. Then, as an admin, try editing that page. Normally, there should be a warning but in vulnerable versions of XWiki, there is no warning.
Patches
This vulnerability has been patched in XWiki 15.10.8 and 16.2.0.
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 script 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-security-requiredrights-default | ≥ 15.9-rc-1&&< 15.10.8 | 15.10.8org.xwiki.platform:xwiki-platform-security-requiredrights-default:15.10.8 |
| ☕Maven | org.xwiki.platform:xwiki-platform-security-requiredrights-default | ≥ 16.0.0-rc-1&&< 16.2.0 | 16.2.0org.xwiki.platform:xwiki-platform-security-requiredrights-default:16.2.0 |
Affected Products
xwikixwikiDetection & 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-security-requiredrights-default, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-security-requiredrights-default to 15.10.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mvgm-3rw2-7j4r is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is GHSA-mvgm-3rw2-7j4r in your dependencies?
Find it across Maven, including transitive dependencies.