How severe is GHSA-vmhh-xh3g-j992?

GHSA-vmhh-xh3g-j992 has a CVSS score of 7.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-vmhh-xh3g-j992?

GHSA-vmhh-xh3g-j992 affects the following packages: org.xwiki.platform:xwiki-platform-flamingo-theme-ui (Maven), org.xwiki.platform:xwiki-platform-flamingo-theme-ui (Maven), org.xwiki.platform:xwiki-platform-flamingo-theme-ui (Maven). Ecosystems affected: Maven.

How do I fix GHSA-vmhh-xh3g-j992?

Update org.xwiki.platform:xwiki-platform-flamingo-theme-ui to 12.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vmhh-xh3g-j992 is resolved across your whole dependency graph.

How do I detect GHSA-vmhh-xh3g-j992 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-flamingo-theme-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-vmhh-xh3g-j992 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-vmhh-xh3g-j992 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vmhh-xh3g-j992 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-vmhh-xh3g-j992?

GHSA-vmhh-xh3g-j992 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 71th 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-vmhh-xh3g-j992?

GHSA-vmhh-xh3g-j992 is classified as CWE-80 (CWE-80), CWE-116 (CWE-116), Cross-site Scripting (XSS) (CWE-79). 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-vmhh-xh3g-j992 published, and has it been updated?

GHSA-vmhh-xh3g-j992 was published on May 25, 2022 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

HIGH severity

Cross-site Scripting in the Flamingo theme managerGHSA-vmhh-xh3g-j992

HIGHFix: xwiki/xwiki-platform@bd93532

GHSA-vmhh-xh3g-j992 is a high-severity (CVSS 7.4) CWE-80 vulnerability in org.xwiki.platform:xwiki-platform-flamingo-theme-ui. A fix is available for org.xwiki.platform:xwiki-platform-flamingo-theme-ui — see the affected versions and patch details below.

Also known asCVE-2022-29251

Published

May 25, 2022

Updated

Nov 8, 2023

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

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

3 pkgs affected

☕org.xwiki.platform:xwiki-platform-flamingo-theme-ui☕org.xwiki.platform:xwiki-platform-flamingo-theme-ui☕org.xwiki.platform:xwiki-platform-flamingo-theme-ui

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

We found a possible XSS vector in the FlamingoThemesCode.WebHomeSheet wiki page related to the "newThemeName" form field.

Patches

The issue is patched in versions 12.10.11, 14.0-rc-1, 13.4.7, 13.10.3.

Workarounds

The easiest workaround is to edit the wiki page FlamingoThemesCode.WebHomeSheet (with wiki editor) and change the line

<input type="hidden" name="newThemeName" id="newThemeName" value="$request.newThemeName" />

into

<input type="hidden" name="newThemeName" id="newThemeName" value="$escapetool.xml($request.newThemeName)" />

References

For more information

If you have any questions or comments about this advisory:

Open an issue in Jira XWiki
Email us at security mailing list

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-flamingo-theme-ui`	all versions	12.10.11`org.xwiki.platform:xwiki-platform-flamingo-theme-ui:12.10.11`
☕Maven	`org.xwiki.platform:xwiki-platform-flamingo-theme-ui`	≥ 13.0.0&&< 13.4.7	13.4.7`org.xwiki.platform:xwiki-platform-flamingo-theme-ui:13.4.7`
☕Maven	`org.xwiki.platform:xwiki-platform-flamingo-theme-ui`	≥ 13.5.0&&< 13.10.3	13.10.3`org.xwiki.platform:xwiki-platform-flamingo-theme-ui:13.10.3`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 13.5 && < 13.10.3

range

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-flamingo-theme-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-flamingo-theme-ui to 12.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vmhh-xh3g-j992 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 We found a possible XSS vector in the `FlamingoThemesCode.WebHomeSheet` wiki page related to the "newThemeName" form field. ### Patches The issue is patched in versions 12.10.11, 14.0-rc-1, 13.4.7, 13.10.3. ### Workarounds The easiest workaround is to edit the wiki page `FlamingoThemesCode.WebHomeSheet` (with wiki editor) and change the line ``` <input type="hidden" name="newThemeName" id="newThemeName" value="$request.newThemeName" /> ``` into ``` <input type="hidden" name="newThemeName" id="newThemeName" value="$escapetool.xml($request.newThemeName)" /> ``` ### References