How severe is GHSA-j9h5-vcgv-2jfm?

GHSA-j9h5-vcgv-2jfm has a CVSS score of 9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-j9h5-vcgv-2jfm?

GHSA-j9h5-vcgv-2jfm affects the following packages: org.xwiki.platform:xwiki-platform-distribution-war (Maven), org.xwiki.platform:xwiki-platform-distribution-war (Maven). Ecosystems affected: Maven.

How do I fix GHSA-j9h5-vcgv-2jfm?

Update org.xwiki.platform:xwiki-platform-distribution-war to 14.4.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j9h5-vcgv-2jfm is resolved across your whole dependency graph.

How do I detect GHSA-j9h5-vcgv-2jfm 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-distribution-war, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j9h5-vcgv-2jfm if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-j9h5-vcgv-2jfm actively exploited in the wild?

No public exploit code has been indexed for GHSA-j9h5-vcgv-2jfm 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-j9h5-vcgv-2jfm?

GHSA-j9h5-vcgv-2jfm has an EPSS (Exploit Prediction Scoring System) score of 70.4%, 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-j9h5-vcgv-2jfm?

GHSA-j9h5-vcgv-2jfm is classified as Cross-site Scripting (XSS) (CWE-79), CWE-116 (CWE-116). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-j9h5-vcgv-2jfm published, and has it been updated?

GHSA-j9h5-vcgv-2jfm was published on May 9, 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

Not in CISA KEV

CRITICAL severity

XWiki Platform vulnerable to RXSS via editor parameter - importinline templateGHSA-j9h5-vcgv-2jfm

CRITICALFix: xwiki/xwiki-platform@28905f7

GHSA-j9h5-vcgv-2jfm is a critical-severity (CVSS 9) Cross-site Scripting (XSS) vulnerability in org.xwiki.platform:xwiki-platform-distribution-war. EPSS puts its 30-day exploitation probability at 70.4% (99th percentile). A fix is available for org.xwiki.platform:xwiki-platform-distribution-war — see the affected versions and patch details below.

Also known asCVE-2023-32071

Published

May 9, 2023

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-j9h5-vcgv-2jfm.

EPSS Exploitation Probability

via FIRST.org ↗

70.4%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.xwiki.platform:xwiki-platform-distribution-war☕org.xwiki.platform:xwiki-platform-distribution-war

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 execute javascript with the right of any user by leading him to a special URL on the wiki targeting a page which contains an attachment.

To reproduce:

add an attachment to a page (for example, your user profile)
add ?xpage=importinline&editor=%22%3E%3Cimg%20src%20onerror=alert(document.domain)%3E to the page view URL as in https://myhost/xwiki/bin/view/XWiki/MyUser?xpage=importinline&editor=%22%3E%3Cimg%20src%20onerror=alert(document.domain)%3E

Patches

This has been patched in XWiki 15.0-rc-1, 14.10.4 and 14.4.8.

Workarounds

The easiest is to edit file <xwiki app>/templates/importinline.vm and apply the modification described on https://github.com/xwiki/xwiki-platform/commit/28905f7f518cc6f21ea61fe37e9e1ed97ef36f01

References

https://jira.xwiki.org/browse/XWIKI-20340 https://app.intigriti.com/company/submissions/e95a7ad5-7029-4627-abf0-3e3e3ea0b4ce/XWIKI-E93DFEYK

Attribution

This vulnerability has been reported on Intigriti by René de Sain @renniepak.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-distribution-war`	≥ 2.2-milestone-1&&< 14.4.8	14.4.8`org.xwiki.platform:xwiki-platform-distribution-war:14.4.8`
☕Maven	`org.xwiki.platform:xwiki-platform-distribution-war`	≥ 14.5&&< 14.10.4	14.10.4`org.xwiki.platform:xwiki-platform-distribution-war:14.10.4`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 14.5.0 && < 14.10.4

1 version

2.2

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-distribution-war, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-distribution-war to 14.4.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j9h5-vcgv-2jfm is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact It's possible to execute javascript with the right of any user by leading him to a special URL on the wiki targeting a page which contains an attachment. To reproduce: * add an attachment to a page (for example, your user profile) * add `?xpage=importinline&editor=%22%3E%3Cimg%20src%20onerror=alert(document.domain)%3E` to the page view URL as in `https://myhost/xwiki/bin/view/XWiki/MyUser?xpage=importinline&editor=%22%3E%3Cimg%20src%20onerror=alert(document.domain)%3E` ### Patches This has been patched in XWiki 15.0-rc-1, 14.10.4 and 14.4.8. ### Workarounds The easiest is to e