GHSA-mgjw-2wrp-r535 is a high-severity (CVSS 8.8) CWE-74 vulnerability in org.xwiki.platform:xwiki-platform-administration-ui. O3 Security confirms whether GHSA-mgjw-2wrp-r535 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Remote code execution in xwiki-platform
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-mgjw-2wrp-r535 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 0 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-administration-uiReal-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
It's possible for an unprivileged user to perform a remote code execution by injecting a groovy script in her own profile and by calling the Reset password feature since the feature is performing a save of the user profile with programming rights in the impacted versions of XWiki.
Patches
The problem has been patched in XWiki 13.1RC1 with a complete refactoring of the Reset password feature.
Workarounds
There's different possible workarounds, all consisting in modifying the XWiki/ResetPassword page.
- the Reset password feature can be entirely disabled by deleting the XWiki/ResetPassword page
- the script in XWiki/ResetPassword can also be modified or removed: an administrator can replace it with a simple email contact to ask an administrator to reset the password.
References
https://jira.xwiki.org/browse/XWIKI-16661
For more information
If you have any questions or comments about this advisory:
- Open an issue in Jira
- Email us at Security mailing-list
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-administration-ui | ≥ 3.1-milestone-1&&< 13.1RC1 | 13.1RC1 |
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-administration-ui. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.xwiki.platform:xwiki-platform-administration-ui to 13.1RC1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mgjw-2wrp-r535 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 pinpoints whether GHSA-mgjw-2wrp-r535 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-mgjw-2wrp-r535. 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-mgjw-2wrp-r535 in your dependencies?
O3 detects GHSA-mgjw-2wrp-r535 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.