CVE-2025-53836: XWiki Rendering is vulnerable to RCE attacks when processing nested macros

Should you act?

Critical, preconditions apply

Severe if exploited, but exploitation needs conditions that may not apply to you. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
• EPSS 0.6%, percentile 50: FIRST’s model estimates a 0.6% chance of exploitation activity in the next 30 days, higher than 50% of all scored CVEs (low). EPSS is a probability, not a verdict.
• Needs an account (low (any account)). Exposure depends on who can log in.
• Only applies if your dependency tree includes org.xwiki.rendering:xwiki-rendering-transformation-macro (Maven) >= 4.2-milestone-1, < 13.10.11, fixed in 13.10.11; org.xwiki.rendering:xwiki-rendering-transformation-macro (Maven) >= 14.0, < 14.4.7, fixed in 14.4.7; org.xwiki.rendering:xwiki-rendering-transformation-macro (Maven) >= 14.5, < 14.10, fixed in 14.10. Check your lockfile, including transitive dependencies.

What it is

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.

From the GitHub advisory

Impact

The default macro content parser didn'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. The following XWiki syntax, when used inside a comment in XWiki, demonstrates the privilege escalation from comment right to programming right and thus remote code execution (RCE) that is possible due to this:

This vulnerability exists since the restricted attribute has been added to the transformation context in version 4.2.

Patches This has been patched in XWiki 13.10.11, 14.4.7 and 14.10.

Workarounds 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.

Weakness type: CWE-863, CWE-94.

Product: org.xwiki.rendering:xwiki-rendering-transformation-macro (Maven) · Assigned by: GitHub_M · Published: 2025-07-14

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: low (any account)
• User interaction: none
• Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
• FIRST EPSS (model of 2026-10-21): 0.64% probability of exploitation activity in the next 30 days; percentile 50.

Timeline

• 2025-07-14 — CVE record published by GitHub_M
• 2025-07-14 — GitHub-reviewed advisory GHSA-32mf-57h2-64x9 published (critical)
• 2025-07-15 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-32mf-57h2-64x9 github.com
2. CVE.org record CVE-2025-53836 cve.org
3. NVD entry CVE-2025-53836 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com
2. github.com github.com
3. jira.xwiki.org jira.xwiki.org
4. jira.xwiki.org jira.xwiki.org

Critical Maven advisories · Today’s Security Digest