GHSA-j584-j2vj-3f93 is a critical-severity (CVSS 9) Code Injection vulnerability in org.xwiki.platform:xwiki-platform-oldcore. A fix is available for org.xwiki.platform:xwiki-platform-oldcore — see the affected versions and patch details below.
XWiki Platform allows remote code execution from user account
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-j584-j2vj-3f93.
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-j584-j2vj-3f93 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 379,145 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-oldcore☕org.xwiki.platform:xwiki-platform-oldcore☕org.xwiki.platform:xwiki-platform-oldcore☕org.xwiki.platform:xwiki-platform-oldcore☕org.xwiki.platform:xwiki-platform-oldcoreReal-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
XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. When an admin disables a user account, the user's profile is executed with the admin's rights. This allows a user to place malicious code in the user profile before getting an admin to disable the user account. To reproduce, as a user without script nor programming rights, edit the about section of your user profile and add {{groovy}}services.logging.getLogger("attacker").error("Hello from Groovy!"){{/groovy}}.
As an admin, go to the user profile and click the "Disable this account" button. Then, reload the page. If the logs show attacker - Hello from Groovy! then the instance is vulnerable. This has been patched in XWiki 14.10.21, 15.5.5, 15.10.6 and 16.0.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Workarounds
We're not aware of any workaround except upgrading.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-oldcore | ≥ 13.4.7&&< 14.10.21 | 14.10.21org.xwiki.platform:xwiki-platform-oldcore:14.10.21 |
| ☕Maven | org.xwiki.platform:xwiki-platform-oldcore | ≥ 13.10.3&&< 14.10.21 | 14.10.21org.xwiki.platform:xwiki-platform-oldcore:14.10.21 |
| ☕Maven | org.xwiki.platform:xwiki-platform-oldcore | ≥ 15.0-rc-1&&< 15.5.5 | 15.5.5org.xwiki.platform:xwiki-platform-oldcore:15.5.5 |
| ☕Maven | org.xwiki.platform:xwiki-platform-oldcore | ≥ 15.6-rc-1&&< 15.10.6 | 15.10.6org.xwiki.platform:xwiki-platform-oldcore:15.10.6 |
| ☕Maven | org.xwiki.platform:xwiki-platform-oldcore | ≥ 16.0.0-rc-1&&< 16.0.0 | 16.0.0org.xwiki.platform:xwiki-platform-oldcore:16.0.0 |
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-oldcore, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-oldcore to 14.10.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j584-j2vj-3f93 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-j584-j2vj-3f93 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-j584-j2vj-3f93. 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-j584-j2vj-3f93 in your dependencies?
O3 Security finds GHSA-j584-j2vj-3f93 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.