How severe is GHSA-6gvj-8vc5-8v3j?

GHSA-6gvj-8vc5-8v3j has a CVSS score of 4.7/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6gvj-8vc5-8v3j?

GHSA-6gvj-8vc5-8v3j affects the following packages: org.xwiki.platform:xwiki-platform-oldcore (Maven). Ecosystems affected: Maven.

How do I fix GHSA-6gvj-8vc5-8v3j?

Update org.xwiki.platform:xwiki-platform-oldcore to 14.10.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6gvj-8vc5-8v3j is resolved across your whole dependency graph.

How do I detect GHSA-6gvj-8vc5-8v3j in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-oldcore. 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.

How do I mitigate GHSA-6gvj-8vc5-8v3j if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-6gvj-8vc5-8v3j?

O3 pinpoints whether GHSA-6gvj-8vc5-8v3j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6gvj-8vc5-8v3j actively exploited in the wild?

No public exploit code has been indexed for GHSA-6gvj-8vc5-8v3j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6gvj-8vc5-8v3j?

GHSA-6gvj-8vc5-8v3j has an EPSS (Exploit Prediction Scoring System) score of 55.1%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-6gvj-8vc5-8v3j?

GHSA-6gvj-8vc5-8v3j is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-6gvj-8vc5-8v3j?

A Nuclei detection template exists for GHSA-6gvj-8vc5-8v3j, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-6gvj-8vc5-8v3j published, and has it been updated?

GHSA-6gvj-8vc5-8v3j was published on May 15, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-6gvj-8vc5-8v3j

MEDIUM

org.xwiki.platform:xwiki-platform-oldcore Open Redirect vulnerability

Also known asCVE-2023-32068

Published

May 15, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

55.1%probability of exploitation in next 30 days

High Risk99th percentile+18.72%

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.

Blast Radius

1 pkg affected

☕org.xwiki.platform:xwiki-platform-oldcore

Real-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 to exploit well known parameters in XWiki URLs to perform redirection to untrusted site. This vulnerability was partially fixed in the past for XWiki 12.10.7 and 13.3RC1 but there is still the possibility to force specific URLs to skip some checks, e.g. using URLs like http:example.com in the parameter would allow the redirect.

Patches

The issue has now been patched against all patterns that we know about for performing redirect. It also performs a real URI parsing that should protect in most cases. This has been patched in XWiki 14.10.4 and 15.0.

Workarounds

The only workaround is to upgrade XWiki.

References

JIRA ticket: https://jira.xwiki.org/browse/XWIKI-20096
JIRA ticket about the improvment actually fixing the vulnerability: https://jira.xwiki.org/browse/XWIKI-20549
Previous advisory about open redirect: https://github.com/advisories/GHSA-jp55-vvmf-63mv

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

Attribution

Thanks to Paulos Mesfin who originally reported the vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-oldcore`	all versions	14.10.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-oldcore. 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-oldcore to 14.10.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6gvj-8vc5-8v3j 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-6gvj-8vc5-8v3j 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-6gvj-8vc5-8v3j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact It's possible to exploit well known parameters in XWiki URLs to perform redirection to untrusted site. This vulnerability was partially fixed in the past for XWiki 12.10.7 and 13.3RC1 but there is still the possibility to force specific URLs to skip some checks, e.g. using URLs like `http:example.com` in the parameter would allow the redirect. ### Patches The issue has now been patched against all patterns that we know about for performing redirect. It also performs a real URI parsing that should protect in most cases. This has been patched in XWiki 14.10.4 and 15.0. ### Worka

O3 Security · Impact-Aware SCA

Is GHSA-6gvj-8vc5-8v3j in your dependencies?

O3 detects GHSA-6gvj-8vc5-8v3j across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-6gvj-8vc5-8v3j

EPSS Exploitation Probability

Blast Radius

Description

Impact

Patches

Workarounds

References

For more information

Attribution

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-6gvj-8vc5-8v3j in your dependencies?