GHSA-xwph-x6xj-wggv is a medium-severity (CVSS 4.7) Open Redirect vulnerability in org.xwiki.platform:xwiki-platform-oldcore. 3 public exploit references exist, so weaponization risk is real. A fix is available for org.xwiki.platform:xwiki-platform-oldcore — see the affected versions and patch details below.
org.xwiki.platform:xwiki-platform-oldcore Open Redirect vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-xwph-x6xj-wggv.
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-xwph-x6xj-wggv 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-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
Impact
It is possible to bypass the existing security measures put in place to avoid open redirect by using a redirect such as //mydomain.com (i.e. omitting the http:). It was also possible to bypass it when using URL such as http:/mydomain.com.
Patches
The problem has been patched on XWiki 13.10.10, 14.4.4 and 14.8RC1.
Workarounds
The only way to workaround the bug is by providing a patched jar of xwiki-platform-oldcore containing the following changes: https://github.com/xwiki/xwiki-platform/commit/e4f7f68e93cb08c25632c126356d218abf192d1e#diff-c445f288d5d63424f56ef13f65514ab4e174a72e979b53b88197c2b7def267cf.
References
- Jira ticket of the reported vulnerability: https://jira.xwiki.org/browse/XWIKI-19994
- Jira ticket of the original mechanism put in place to prevent open redirect: https://jira.xwiki.org/browse/XWIKI-10309
- Original advisory about open redirect: https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-jp55-vvmf-63mv
For more information
If you have any questions or comments about this advisory:
- Open an issue in Jira
- Email us at Security ML
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-oldcore | ≥ 6.0-rc-1&&< 13.10.10 | 13.10.10org.xwiki.platform:xwiki-platform-oldcore:13.10.10 |
| ☕Maven | org.xwiki.platform:xwiki-platform-oldcore | ≥ 14.0-rc-1&&< 14.4.4 | 14.4.4org.xwiki.platform:xwiki-platform-oldcore:14.4.4 |
| ☕Maven | org.xwiki.platform:xwiki-platform-oldcore | ≥ 14.5&&< 14.8-rc-1 | 14.8-rc-1org.xwiki.platform:xwiki-platform-oldcore:14.8-rc-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-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 13.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xwph-x6xj-wggv 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-xwph-x6xj-wggv can be triaged on real exposure rather than presence alone.
Tailored to GHSA-xwph-x6xj-wggv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect GHSA-xwph-x6xj-wggv
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-xwph-x6xj-wggv -u https://target- Template
- XWiki - Open Redirect
- Severity
- medium
- Impact
- An attacker can redirect users to malicious websites, leading to phishing attacks or malware downloads.
- Remediation
- Implement proper input validation and sanitize user-controlled input to prevent open redirect vulnerabilities.
Template by ProjectDiscovery nuclei-templates (ritikchaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is GHSA-xwph-x6xj-wggv in your dependencies?
O3 Security finds GHSA-xwph-x6xj-wggv across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.