GHSA-g75c-cjr6-39mc is a critical-severity (CVSS 9.9) Improper Privilege Management vulnerability in org.xwiki.platform:xwiki-platform-mail-send-default. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.xwiki.platform:xwiki-platform-mail-send-default — see the affected versions and patch details below.
XWiki Platform's Mail.MailConfig can be edited by any user with edit rights
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-g75c-cjr6-39mc.
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-g75c-cjr6-39mc 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,333 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-mail-send-default☕org.xwiki.platform:xwiki-platform-mail-send-default☕org.xwiki.platform:xwiki-platform-mail-send-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
Mail.MailConfig can be edited by any logged-in user by default. Consequently, they can:
- change the mail obfuscation configuration
- view and edit the mail sending configuration, including the smtp domain name and credentials.
Patches
The problem has been patched on XWiki 14.4.8, 15.1, and 14.10.6.
Workarounds
The rights of the Mail.MailConfig page can be manually updated so that only a set of trusted users can view, edit and delete it (e.g., the XWiki.XWikiAdminGroup group).
On 14.4.8+, 15.1-rc-1+, or 14.10.5+, if at startup Mail.MailConfig does not have any rights defined, view, edit and delete rights are automatically granted to the XWiki.XWikiAdminGroup group.
See the corresponding patch.
References
- https://jira.xwiki.org/browse/XWIKI-20519 + https://jira.xwiki.org/browse/XWIKI-20671
- https://github.com/xwiki/xwiki-platform/commit/d28d7739089e1ae8961257d9da7135d1a01cb7d4
- https://github.com/xwiki/xwiki-platform/commit/8910b8857d3442d2e8142f655fdc0512930354d1
For more information
If you have any questions or comments about this advisory:
- Open an issue in Jira XWiki.org
- Email us at Security Mailing List
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-mail-send-default | ≥ 11.8-rc-1&&< 14.4.8 | 14.4.8org.xwiki.platform:xwiki-platform-mail-send-default:14.4.8 |
| ☕Maven | org.xwiki.platform:xwiki-platform-mail-send-default | ≥ 14.5&&< 14.10.6 | 14.10.6org.xwiki.platform:xwiki-platform-mail-send-default:14.10.6 |
| ☕Maven | org.xwiki.platform:xwiki-platform-mail-send-default | ≥ 15.0-rc-1&&< 15.1 | 15.1org.xwiki.platform:xwiki-platform-mail-send-default:15.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
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-mail-send-default, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-mail-send-default to 14.4.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g75c-cjr6-39mc 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-g75c-cjr6-39mc can be triaged on real exposure rather than presence alone.
Tailored to GHSA-g75c-cjr6-39mc. 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-g75c-cjr6-39mc in your dependencies?
O3 Security finds GHSA-g75c-cjr6-39mc across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.