xwiki-rendering: Improper Control of Generation of Code
CVE-2025-53836 is a high-severity improper control of generation of code vulnerability in xwiki-rendering from XWiki, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected xwiki-rendering versions: >= 4.2-milestone-1, < 13.10.11; >= 14.0, < 14.4.7; >= 14.5, < 14.10. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.64% chance of exploitation within 30 days, higher than 51% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Xwiki to 13.10.11 or 14.4.7 or 14.10, whichever matches your release line, or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| XWiki | xwiki-rendering | >= 4.2-milestone-1, < 13.10.11; >= 14.0, < 14.4.7; >= 14.5, < 14.10 | Not stated |
| XWiki | Xwiki | 4.3 up to, but not including, 13.10.11; 14.0 up to, but not including, 14.4.7; 14.5 up to, but not including, 14.10; 4.2 | 13.10.11, 14.4.7, 14.10 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.9 | Critical | CNA (github.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
XWiki Rendering is a generic rendering system that converts textual input in a given syntax (wiki syntax, HTML, etc) into another syntax (XHTML, etc). Starting in version 4.2-milestone-1 and prior to versions 13.10.11, 14.4.7, and 14.10, the default macro content parser doesn't preserve the restricted attribute of the transformation context when executing nested macros. This allows executing macros that are normally forbidden in restricted mode, in particular script macros. The cache and chart macros that are bundled in XWiki use the vulnerable feature. This has been patched in XWiki 13.10.11, 14.4.7 and 14.10. To avoid the exploitation of this bug, comments can be disabled for untrusted users until an upgrade to a patched version has been performed. Note that users with edit rights will still be able to add comments via the object editor even if comments have been disabled.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Generation of Code
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How developers prevent this class of flaw
- Refactor your program so that you do not have to dynamically generate code.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
More Improper Control of Generation of Code vulnerabilities (CWE-94)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/xwiki/xwiki-rendering/security/advisories/GHSA-32mf-57h2-64x9Third Party Advisory
Patches and release notes
Technical write-ups (may include proof of concept)
- jira.xwiki.org/browse/XRENDERING-689Exploit, Issue Tracking
- jira.xwiki.org/browse/XWIKI-20375Exploit, Issue Tracking
Other vulnerabilities in xwiki-rendering
- 9.9 Critical severity
- 8.8 High severity
- 9.0 Critical severity
- 8.8 High severity
- 9.6 Critical severity
Recent Improper Control of Generation of Code vulnerabilities
- 9.8 Critical severity
- 7.2 High severity
- 9.8 Critical severity
- 10.0 Critical severity
- 8.6 High severity
- 8.8 High severity
Microsoft SharePoint Code Injection Exploited
Spotted an error? Tell us.