How severe is GHSA-h63h-5c77-77p5?

GHSA-h63h-5c77-77p5 has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-h63h-5c77-77p5?

GHSA-h63h-5c77-77p5 affects the following packages: org.xwiki.platform:xwiki-platform-search-ui (Maven), org.xwiki.platform:xwiki-platform-search-ui (Maven), org.xwiki.platform:xwiki-platform-search-ui (Maven). Ecosystems affected: Maven.

How do I fix GHSA-h63h-5c77-77p5?

Update org.xwiki.platform:xwiki-platform-search-ui to 14.10.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h63h-5c77-77p5 is resolved across your whole dependency graph.

How do I detect GHSA-h63h-5c77-77p5 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-search-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-h63h-5c77-77p5 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-h63h-5c77-77p5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-h63h-5c77-77p5 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-h63h-5c77-77p5?

GHSA-h63h-5c77-77p5 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th 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-h63h-5c77-77p5?

GHSA-h63h-5c77-77p5 is classified as CWE-95 (CWE-95), CWE-862 (CWE-862), Code Injection (CWE-94). 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-h63h-5c77-77p5 published, and has it been updated?

GHSA-h63h-5c77-77p5 was published on July 31, 2024 and was last updated on September 6, 2024. 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 remote code execution from account via SearchSuggestConfigSheetGHSA-h63h-5c77-77p5

CRITICALFix: xwiki/xwiki-platform@0b13576

GHSA-h63h-5c77-77p5 is a critical-severity (CVSS 9.9) CWE-95 vulnerability in org.xwiki.platform:xwiki-platform-search-ui. A fix is available for org.xwiki.platform:xwiki-platform-search-ui — see the affected versions and patch details below.

Also known asCVE-2024-37901

Published

Jul 31, 2024

Updated

Sep 6, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 10, 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-h63h-5c77-77p5.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% 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-search-ui☕org.xwiki.platform:xwiki-platform-search-ui☕org.xwiki.platform:xwiki-platform-search-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

Any user with edit right on any page can perform arbitrary remote code execution by adding instances of XWiki.SearchSuggestConfig and XWiki.SearchSuggestSourceClass to their user profile or any other page. This compromises the confidentiality, integrity and availability of the whole XWiki installation.

To reproduce on an instance, as a user without script nor programming rights, add an object of type XWiki.SearchSuggestConfig to your profile page, and an object of type XWiki.SearchSuggestSourceClass as well. On this last object, set both name and icon properties to $services.logging.getLogger("attacker").error("I got programming: $services.security.authorization.hasAccess('programming')") and limit and engine to {{/html}}{{async}}{{velocity}}$services.logging.getLogger("attacker").error("I got programming: $services.security.authorization.hasAccess('programming')"){{/velocity}}{{/async}}. Save and display the page. If the logs contain any message ERROR attacker - I got programming: true then the instance is vulnerable.

Patches

This vulnerability has been patched in XWiki 14.10.21, 15.5.5 and 15.10.2.

Workarounds

We're not aware of any workaround except upgrading.

References

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-search-ui`	≥ 9.2-rc-1&&< 14.10.21	14.10.21`org.xwiki.platform:xwiki-platform-search-ui:14.10.21`
☕Maven	`org.xwiki.platform:xwiki-platform-search-ui`	≥ 15.0-rc-1&&< 15.5.5	15.5.5`org.xwiki.platform:xwiki-platform-search-ui:15.5.5`
☕Maven	`org.xwiki.platform:xwiki-platform-search-ui`	≥ 15.6-rc-1&&< 15.10.2	15.10.2`org.xwiki.platform:xwiki-platform-search-ui:15.10.2`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 15.6 && < 15.10.2

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-search-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-search-ui to 14.10.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h63h-5c77-77p5 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### Impact Any user with edit right on any page can perform arbitrary remote code execution by adding instances of `XWiki.SearchSuggestConfig` and `XWiki.SearchSuggestSourceClass` to their user profile or any other page. This compromises the confidentiality, integrity and availability of the whole XWiki installation. To reproduce on an instance, as a user without script nor programming rights, add an object of type `XWiki.SearchSuggestConfig` to your profile page, and an object of type `XWiki.SearchSuggestSourceClass` as well. On this last object, set both `name` and `icon` properties to `$se