dbcve.org
Xwiki RenderingApplication · Xwiki

CVE-2025-66474

HIGH · 8.8 CVSS v3.1 Published 2025-12-10
Fix available
A fix is available. Upgrade to 16.10.10 / 17.4.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
XWiki Rendering is a generic rendering system that converts textual input in a given syntax (wiki syntax, HTML, etc) into another syntax (XHTML, etc). Versions 16.10.9 and below, 17.0.0-rc-1 through 17.4.2 and 17.5.0-rc-1 through 17.5.0 have insufficient protection against {{/html}} injection, which attackers can exploit through RCE. Any user who can edit their own profile or any other document can execute arbitrary script macros, including Groovy and Python macros, which enable remote code execution as well as unrestricted read and write access to all wiki contents. This issue is fixed in versions 16.10.10, 17.4.3 and 17.6.0-rc-1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Xwiki RenderingApplication
Affected:< 16.10.10>= 17.0.0, < 17.4.3= 17.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 16.10.10 / 17.4.3 or later
Fixed in 16.10.1017.4.3
Vendor patch github.com →
Recommended fix High confidence

Upgrade to XWiki Rendering 16.10.10 (for 16.x branch) or 17.4.3 (for 17.x branch)

  1. Identify the current XWiki Rendering version in use by checking the project's dependencies or pom.xml
  2. Determine which release branch is in use (16.x or 17.x)
  3. For 16.x branch: Upgrade to version 16.10.10 or later
  4. For 17.x branch: Upgrade to version 17.4.3 or later
  5. Update the dependency in pom.xml or build configuration: Change xwiki-platform-rendering-*-16.10.9 to 16.10.10, or xwiki-platform-rendering-*-17.4.2 to 17.4.3 (or 17.6.0-rc-1 if on 17.x and wanting latest)
  6. Run build and tests to verify compatibility
  7. Deploy the updated version to staging/QA environment
  8. Verify the fix by testing that {{/html}} injection is properly blocked
Caveat As with any minor version upgrade, test thoroughly in a non-production environment first to ensure no rendering macros or wiki syntax behave unexpectedly

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66474 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-66474 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data