How severe is GHSA-j2pq-22jj-4pm5?

GHSA-j2pq-22jj-4pm5 has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-j2pq-22jj-4pm5?

GHSA-j2pq-22jj-4pm5 affects the following packages: org.xwiki.platform:xwiki-platform-repository-server-ui (Maven), org.xwiki.platform:xwiki-platform-repository-server-ui (Maven). Ecosystems affected: Maven.

How do I fix GHSA-j2pq-22jj-4pm5?

Update org.xwiki.platform:xwiki-platform-repository-server-ui to 15.10.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j2pq-22jj-4pm5 is resolved across your whole dependency graph.

How do I detect GHSA-j2pq-22jj-4pm5 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-repository-server-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j2pq-22jj-4pm5 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-j2pq-22jj-4pm5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-j2pq-22jj-4pm5 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-j2pq-22jj-4pm5?

GHSA-j2pq-22jj-4pm5 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th 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-j2pq-22jj-4pm5?

GHSA-j2pq-22jj-4pm5 is classified as CWE-96 (CWE-96), CWE-863 (CWE-863), 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-j2pq-22jj-4pm5 published, and has it been updated?

GHSA-j2pq-22jj-4pm5 was published on December 12, 2024 and was last updated on December 12, 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 allows remote code execution through the extension sheetGHSA-j2pq-22jj-4pm5

CRITICALFix: xwiki/xwiki-platform@8659f17

GHSA-j2pq-22jj-4pm5 is a critical-severity (CVSS 9.9) CWE-96 vulnerability in org.xwiki.platform:xwiki-platform-repository-server-ui. A fix is available for org.xwiki.platform:xwiki-platform-repository-server-ui — see the affected versions and patch details below.

Also known asCVE-2024-55662

Published

Dec 12, 2024

Updated

Dec 12, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-j2pq-22jj-4pm5.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% 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-repository-server-ui☕org.xwiki.platform:xwiki-platform-repository-server-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

On instances where Extension Repository Application is installed, any user can execute any code requiring programming rights on the server. In order to reproduce on an instance, as a normal user without script nor programming rights, go to your profile and add an object of type ExtensionCode.ExtensionClass. Set the description to {{async}}{{groovy}}println("Hello from Description"){{/groovy}}{{/async}} and press Save and View. If the description displays as Hello from Description without any error, then the instance is vulnerable.

Patches

This vulnerability has been fixed in XWiki 15.10.9 and 16.3.0.

Workarounds

Since Extension Repository Application is not mandatory, it can be safely disabled on instances that do not use it. It is also possible to manually apply this patch to the page ExtensionCode.ExtensionSheet, as well as this patch to the page ExtensionCode.ExtensionAuthorsDisplayer.

References

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-repository-server-ui`	≥ 3.3-milestone-1&&< 15.10.9	15.10.9`org.xwiki.platform:xwiki-platform-repository-server-ui:15.10.9`
☕Maven	`org.xwiki.platform:xwiki-platform-repository-server-ui`	≥ 16.0.0-rc-1&&< 16.3.0	16.3.0`org.xwiki.platform:xwiki-platform-repository-server-ui:16.3.0`

Affected Products

1 product · 2 configurations

Application

xwikixwiki

≥ 16.0.0 && < 16.3.0

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-repository-server-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-repository-server-ui to 15.10.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j2pq-22jj-4pm5 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 On instances where `Extension Repository Application` is installed, any user can execute any code requiring `programming` rights on the server. In order to reproduce on an instance, as a normal user without `script` nor `programming` rights, go to your profile and add an object of type `ExtensionCode.ExtensionClass`. Set the description to `{{async}}{{groovy}}println("Hello from Description"){{/groovy}}{{/async}}` and press `Save and View`. If the description displays as `Hello from Description` without any error, then the instance is vulnerable. ### Patches This vulnerability has