Skip to content
Fencer Vulns
critical 9.9

CVE-2023-29511 json

xwiki-platform-administration-ui vulnerable to privilege escalation

published 2023-04-12 3 y ago modified 2026-09-10 1 mo ago also GHSA-rfh6-mg6h-h668 , EUVD-2023-1391

cvss
9.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 64%
public exploits
0
none known

Summary

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. Any user with edit rights on a page (e.g., it's own user page), can execute arbitrary Groovy, Python or Velocity code in XWiki leading to full access to the XWiki installation. The root cause is improper escaping of the section ids in `XWiki.AdminFieldsDisplaySheet`. This page is installed by default. The vulnerability has been patched in XWiki versions 15.0-rc-1, 14.10.1, 14.4.8, and 13.10.11.

Patch / fix

  • maven org.xwiki.platform:xwiki-platform-administration-ui 13.10.11, 14.4.8, 14.10.1
  • xwiki xwiki 13.10.11, 14.4.8, 14.10.1

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
21 mo ago

Exploit prediction

1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • jira.xwiki.org https://jira.xwiki.org/browse/XWIKI-20261 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L

Affected packages

ecosystem package affected fixed in
maven org.xwiki.platform:xwiki-platform-administration-ui
>=1.5M2, <13.10.11
>=14.0-rc-1, <14.4.8
>=14.5, <14.10.1
13.10.11
14.4.8
14.10.1

Affected products

  • xwiki xwiki-platform

Classification

Weakness
  • CWE-95 Improper Neutralization of Directives in Dynamically Evaluated Code

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.