How severe is GHSA-qj86-p74r-7wp5?

GHSA-qj86-p74r-7wp5 has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-qj86-p74r-7wp5?

GHSA-qj86-p74r-7wp5 affects the following packages: org.xwiki.platform:xwiki-platform-administration-ui (Maven), org.xwiki.platform:xwiki-platform-administration-ui (Maven), org.xwiki.platform:xwiki-platform-administration-ui (Maven). Ecosystems affected: Maven.

How do I fix GHSA-qj86-p74r-7wp5?

Update org.xwiki.platform:xwiki-platform-administration-ui to 14.10.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qj86-p74r-7wp5 is resolved across your whole dependency graph.

How do I detect GHSA-qj86-p74r-7wp5 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-administration-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qj86-p74r-7wp5 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-qj86-p74r-7wp5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qj86-p74r-7wp5 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-qj86-p74r-7wp5?

GHSA-qj86-p74r-7wp5 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 68th 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-qj86-p74r-7wp5?

GHSA-qj86-p74r-7wp5 is classified as Code Injection (CWE-94), CWE-95 (CWE-95). 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-qj86-p74r-7wp5 published, and has it been updated?

GHSA-qj86-p74r-7wp5 was published on December 16, 2023 and was last updated on September 10, 2026. 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

Remote code execution/programming rights with configuration section from any user accountGHSA-qj86-p74r-7wp5

CRITICALFix: xwiki/xwiki-platform@0f367aa

GHSA-qj86-p74r-7wp5 is a critical-severity (CVSS 9.9) Code Injection vulnerability in org.xwiki.platform:xwiki-platform-administration-ui. A fix is available for org.xwiki.platform:xwiki-platform-administration-ui — see the affected versions and patch details below.

Also known asCVE-2023-50723

Published

Dec 16, 2023

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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-qj86-p74r-7wp5.

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% 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-administration-ui☕org.xwiki.platform:xwiki-platform-administration-ui☕org.xwiki.platform:xwiki-platform-administration-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

Anyone who can edit an arbitrary wiki page in an XWiki installation can gain programming right through several cases of missing escaping in the code for displaying sections in the administration interface. This impacts the confidentiality, integrity and availability of the whole XWiki installation. Normally, all users are allowed to edit their own user profile so this should be exploitable by all users of the XWiki instance.

The easiest way to reproduce this is to edit any document with the object editor and add an object of type XWiki.ConfigurableClass ("Custom configurable sections"). Set "Display in section" and "Display in Category" to "other", set scope to "Wiki and all spaces" and "Heading" to {{async}}{{groovy}}services.logging.getLogger("attacker").error("Attack from Heading succeeded!"); println("Hello from Groovy!"){{/groovy}}{{/async}}. Click "Save". Open <xwiki-host>/xwiki/bin/view/Main/?sheet=XWiki.AdminSheet&viewer=content&editor=globaladmin&section=other where <xwiki-host> is the URL of your XWiki installation. If this displays just "Hello from Groovy!" in a heading and generates an error message with content "Attack from Heading succeeded!" in XWiki's log, the attack succeeded. Similar attacks are also possible by creating this kind of object on a document with a specially crafted name, see the referenced Jira issues for more reproduction steps.

Patches

This has been fixed in XWiki 14.10.15, 15.5.2 and 15.7RC1

Workarounds

It is possible to manually apply the fixes for the vulnerability by editing two pages in the wiki. This patch needs to be applied to the page XWiki.ConfigurableClassMacros. Further, the following patches need to be applied to the page XWiki.ConfigurableClass:

Note that also the page XWiki.ConfigurableClass needs to be changed to xwiki/2.1 syntax for the escaping to work properly but the security vulnerability is fixed also without changing the syntax.

References

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-administration-ui`	≥ 2.3&&< 14.10.15	14.10.15`org.xwiki.platform:xwiki-platform-administration-ui:14.10.15`
☕Maven	`org.xwiki.platform:xwiki-platform-administration-ui`	≥ 15.0-rc-1&&< 15.5.2	15.5.2`org.xwiki.platform:xwiki-platform-administration-ui:15.5.2`
☕Maven	`org.xwiki.platform:xwiki-platform-administration-ui`	≥ 15.6-rc-1&&< 15.7-rc-1	15.7-rc-1`org.xwiki.platform:xwiki-platform-administration-ui:15.7-rc-1`

Affected Products

1 product · 5 configurations

Application

xwikixwiki

≥ 15.0 && < 15.5.2

2 versions

15.615.7

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-administration-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-administration-ui to 14.10.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qj86-p74r-7wp5 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 Anyone who can edit an arbitrary wiki page in an XWiki installation can gain programming right through several cases of missing escaping in the code for displaying sections in the administration interface. This impacts the confidentiality, integrity and availability of the whole XWiki installation. Normally, all users are allowed to edit their own user profile so this should be exploitable by all users of the XWiki instance. The easiest way to reproduce this is to edit any document with the object editor and add an object of type `XWiki.ConfigurableClass` ("Custom configurable sec