How severe is GHSA-cmvg-w72j-7phx?

GHSA-cmvg-w72j-7phx has a CVSS score of 9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-cmvg-w72j-7phx?

GHSA-cmvg-w72j-7phx affects the following packages: org.xwiki.platform:xwiki-platform-skin-skinx (Maven). Ecosystems affected: Maven.

How do I fix GHSA-cmvg-w72j-7phx?

Update org.xwiki.platform:xwiki-platform-skin-skinx to 14.9-rc-1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cmvg-w72j-7phx is resolved across your whole dependency graph.

How do I detect GHSA-cmvg-w72j-7phx 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-skin-skinx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cmvg-w72j-7phx 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-cmvg-w72j-7phx actively exploited in the wild?

Yes. There are 4 known exploit references for GHSA-cmvg-w72j-7phx, including 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-cmvg-w72j-7phx?

GHSA-cmvg-w72j-7phx has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 61th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-cmvg-w72j-7phx?

GHSA-cmvg-w72j-7phx is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type 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-cmvg-w72j-7phx published, and has it been updated?

GHSA-cmvg-w72j-7phx was published on April 12, 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

org.xwiki.platform:xwiki-platform-skin-skinx vulnerable to basic Cross-site Scripting by exploiting JSX or SSX pluginsGHSA-cmvg-w72j-7phx

CRITICALFix: xwiki/xwiki-platform@fe65bc3

GHSA-cmvg-w72j-7phx is a critical-severity (CVSS 9) Cross-site Scripting (XSS) vulnerability in org.xwiki.platform:xwiki-platform-skin-skinx. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.xwiki.platform:xwiki-platform-skin-skinx — see the affected versions and patch details below.

Also known asCVE-2023-29206

Published

Apr 12, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

Exploitation data as of Nov 7, 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-cmvg-w72j-7phx.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs61th percentile — riskier than 61% 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

1 pkg affected

☕org.xwiki.platform:xwiki-platform-skin-skinx

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

There was no check in the author of a JavaScript xobject or StyleSheet xobject added in a XWiki document, so until now it was possible for a user having only Edit Right to create such object and to craft a script allowing to perform some operations when executing by a user with appropriate rights.

Patches

This has been patched in XWiki 14.9-rc-1 by only executing the script if the author of it has Script right.

Workarounds

The only known workaround consists in applying the following patch and rebuilding and redeploying xwiki-platform-skin-skinx.

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-skin-skinx`	≥ 3.0-milestone-1&&< 14.9-rc-1	14.9-rc-1`org.xwiki.platform:xwiki-platform-skin-skinx:14.9-rc-1`

Affected Products

1 product · 5 configurations

Application

xwikixwiki

> 3.0 && ≤ 14.8

1 version

3.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

XWiki Commons are technical libraries common to several other top level …

jira.xwiki.orgNVDApr 2023

Report on github.com

github.comNVDApr 2023

Report on jira.xwiki.org

jira.xwiki.orgNVDApr 2023

Report on jira.xwiki.org

jira.xwiki.orgNVDApr 2023

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-skin-skinx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-skin-skinx to 14.9-rc-1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cmvg-w72j-7phx 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 There was no check in the author of a JavaScript xobject or StyleSheet xobject added in a XWiki document, so until now it was possible for a user having only Edit Right to create such object and to craft a script allowing to perform some operations when executing by a user with appropriate rights. ### Patches This has been patched in XWiki 14.9-rc-1 by only executing the script if the author of it has Script right. ### Workarounds The only known workaround consists in applying [the following patch](https://github.com/xwiki/xwiki-platform/commit/fe65bc35d5672dd2505b7ac4ec42aec