How severe is CVE-2025-66474?

No CVSS score has been assigned to CVE-2025-66474 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-66474?

CVE-2025-66474 affects the following packages: org.xwiki.rendering:xwiki-rendering-xml (Maven), org.xwiki.rendering:xwiki-rendering-xml (Maven), org.xwiki.rendering:xwiki-rendering-xml (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-66474?

Update org.xwiki.rendering:xwiki-rendering-xml to 16.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-66474 is resolved across your whole dependency graph.

How do I detect CVE-2025-66474 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.rendering:xwiki-rendering-xml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-66474 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-66474?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-66474 can be triaged on real exposure rather than presence alone.

Is CVE-2025-66474 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-66474 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-66474?

CVE-2025-66474 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-66474?

CVE-2025-66474 is classified as CWE-95 (CWE-95), Code Injection (CWE-94). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-66474 published, and has it been updated?

CVE-2025-66474 was published on December 10, 2025 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2025-66474 — xwiki-rendering-xml

Fix: xwiki/xwiki-platform@12b780c

CVE-2025-66474 is a CWE-95 vulnerability in org.xwiki.rendering:xwiki-rendering-xml. A fix is available for org.xwiki.rendering:xwiki-rendering-xml — see the affected versions and patch details below.

XWiki vulnerable to remote code execution through insufficient protection against {{/html}} injection

Also known asGHSA-9xc6-c2rm-f27p

Published

Dec 10, 2025

Updated

Aug 12, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-66474.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

3 pkgs affected

☕org.xwiki.rendering:xwiki-rendering-xml☕org.xwiki.rendering:xwiki-rendering-xml☕org.xwiki.rendering:xwiki-rendering-xml

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Any user who can edit their own user profile or any other document can execute arbitrary script macros including Groovy and Python macros that allow remote code execution including unrestricted read and write access to all wiki contents. The reason is that rendering output is included as content of HTML macros with insufficient escaping, and it is thus possible to close the HTML macro and inject script macros that are executed with programming rights. To demonstrate, the content {{html}}{{/html {{/html}}}} can be inserted into any field of the user profile that supports wiki syntax like the "About" field. If this leads to the display of raw HTML, the instance is vulnerable.

Patches

This problem has been patched by extending the escaping introduced by XRENDERING-693 to also cover closing HTML macros that have spaces after the macro name in XWiki 16.10.10, 17.4.3 and 17.6.0RC1. A similar fix has been applied in org.xwiki.platform:xwiki-platform-oldcore as an extra safety net, see XWIKI-23378. At this point, we're not aware that this extra safety net would be required for security.

The patch also fixes the injection of opening HTML macro syntaxes, e.g., with {{html}}{{html{{/html}}}} which disrupts the rendering of the user profile but for which we haven't found any further security impact apart from the disruption of the UI.

Workarounds

We're not aware of any workarounds except for upgrading the affected module to a version with a fix.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.rendering:xwiki-rendering-xml`	all versions	16.10.10`org.xwiki.rendering:xwiki-rendering-xml:16.10.10`
☕Maven	`org.xwiki.rendering:xwiki-rendering-xml`	≥ 17.0.0-rc-1&&< 17.4.3	17.4.3`org.xwiki.rendering:xwiki-rendering-xml:17.4.3`
☕Maven	`org.xwiki.rendering:xwiki-rendering-xml`	≥ 17.5.0-rc-1&&< 17.6.0-rc-1	17.6.0-rc-1`org.xwiki.rendering:xwiki-rendering-xml:17.6.0-rc-1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.rendering:xwiki-rendering-xml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.rendering:xwiki-rendering-xml to 16.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-66474 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-66474 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-66474. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Any user who can edit their own user profile or any other document can execute arbitrary script macros including Groovy and Python macros that allow remote code execution including unrestricted read and write access to all wiki contents. The reason is that rendering output is included as content of HTML macros with insufficient escaping, and it is thus possible to close the HTML macro and inject script macros that are executed with programming rights. To demonstrate, the content `{{html}}{{/html {{/html}}}}` can be inserted into any field of the user profile that supports wiki synta

O3 Security · Impact-Aware SCA

Is CVE-2025-66474 in your dependencies?

O3 Security finds CVE-2025-66474 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

CVE-2025-66474 — xwiki-rendering-xml

Exploitation Status

Proof-of-concept exploit code exists

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Workarounds

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is CVE-2025-66474 in your dependencies?