Skip to content
Fencer Vulns
critical 9.1

CVE-2023-40572 json

XWiki Platform vulnerable to CSRF privilege escalation/RCE via the create action

published 2023-08-23 3 y ago modified 2026-09-10 1 mo ago also GHSA-4f8m-7h83-9f6m , EUVD-2023-2206

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

Summary

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. The create action is vulnerable to a CSRF attack, allowing script and thus remote code execution when targeting a user with script/programming right, thus compromising the confidentiality, integrity and availability of the whole XWiki installation. When a user with script right views this image and a log message `ERROR foo - Script executed!` appears in the log, the XWiki installation is vulnerable. This has been patched in XWiki 14.10.9 and 15.4RC1 by requiring a CSRF token for the actual page creation.

Patch / fix

  • maven org.xwiki.platform:xwiki-platform-oldcore 14.10.9, 15.4-rc-1
  • xwiki xwiki 14.10.9

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

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

Exploits and checks

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.xwiki.platform:xwiki-platform-oldcore
>=3.2-milestone-3, <14.10.9
>=15.0-rc-1, <15.4-rc-1
14.10.9
15.4-rc-1

Affected products

  • xwiki xwiki-platform

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

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.