Skip to content
Fencer Vulns
critical 10.0

CVE-2023-26474 json

XWiki Platform vulnerable to privilege escalation via properties with wiki syntax that are executed with wrong author

published 2023-03-02 3 y ago modified 2026-09-10 1 mo ago also GHSA-3738-p9x3-mv9r , EUVD-2023-0846

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

Summary

XWiki Platform is a generic wiki platform. Starting in version 13.10, it's possible to use the right of an existing document content author to execute a text area property. This has been patched in XWiki 14.10, 14.4.7, and 13.10.11. There are no known workarounds.

Patch / fix

  • maven org.xwiki.platform:xwiki-platform-oldcore 13.10.11, 14.4.7, 14.10
  • maven org.xwiki.platform:xwiki-platform-legacy-oldcore 13.10.11, 14.4.7, 14.10
  • xwiki xwiki 13.10.11, 14.4.7, 14.10

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
20 mo ago

Exploit prediction

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

Exploits and checks

  • jira.xwiki.org https://jira.xwiki.org/browse/XWIKI-20373 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-3738-p9x3-mv9r referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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:H

Affected packages

ecosystem package affected fixed in
maven org.xwiki.platform:xwiki-platform-oldcore
>=13.10, <13.10.11
>=14.0, <14.4.7
>=14.5, <14.10
13.10.11
14.4.7
14.10
maven org.xwiki.platform:xwiki-platform-legacy-oldcore
>=13.10, <13.10.11
>=14.0, <14.4.7
>=14.5, <14.10
13.10.11
14.4.7
14.10

Affected products

  • xwiki xwiki-platform

Classification

Weakness

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.