Skip to content
Fencer Vulns
critical 9.1

CVE-2023-37908 json

org.xwiki.rendering:xwiki-rendering-xml Improper Neutralization of Invalid Characters in Identifiers in Web Pages vulnerability

published 2023-10-25 3 y ago modified 2026-06-17 4 mo ago also GHSA-663w-2xp3-5739 , EUVD-2023-2666

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

Summary

XWiki Rendering is a generic Rendering system that converts textual input in a given syntax into another syntax. The cleaning of attributes during XHTML rendering, introduced in version 14.6-rc-1, allowed the injection of arbitrary HTML code and thus cross-site scripting via invalid attribute names. This can be exploited, e.g., via the link syntax in any content that supports XWiki syntax like comments in XWiki. When a user moves the mouse over a malicious link, the malicious JavaScript code is executed in the context of the user session. When this user is a privileged user who has programming rights, this allows server-side code execution with programming rights, impacting the confidentiality, integrity and availability of the XWiki instance. While this attribute was correctly recognized as not allowed, the attribute was still printed with a prefix `data-xwiki-translated-attribute-` without further cleaning or validation. This problem has been patched in XWiki 14.10.4 and 15.0 RC1 by removing characters not allowed in data attributes and then validating the cleaned attribute again. There are no known workarounds apart from upgrading to a version including the fix.

Patch / fix

  • maven org.xwiki.rendering:xwiki-rendering-xml 14.10.4
  • xwiki xwiki-rendering 14.10.4

CISA SSVC

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

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/xwiki/xwiki-rendering/security/advisories/GHSA-663w-2xp3-5739 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/xwiki/xwiki-rendering/security/advisories/GHSA-6gf5-c898-7rxp referenced PoC, tagged "exploit" by a source, unverified
  • jira.xwiki.org https://jira.xwiki.org/browse/XRENDERING-697 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 9.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
GitHub 3.1 9.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.xwiki.rendering:xwiki-rendering-xml
>=14.6-rc-1, <14.10.4
14.10.4

Affected products

  • xwiki xwiki-rendering

Classification

Weakness
  • CWE-83 Improper Neutralization of Script in Attributes in a Web Page
  • CWE-79 Improper Neutralization of Input During Web Page Generation
  • CWE-86 Improper Neutralization of Invalid Characters in Identifiers in Web Pages

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.