high CVSS 8.8

CVE-2025-66474·Python vulnerability

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.

Severity
high
Software
Python
Fixed in
17.4.3
Published
2025-12-10

Affected versions

From: 17.0.0

Until: 17.4.3

Fixed in: 17.4.3

How to fix this CVE

Update XWiki Rendering to version 17.4.3 or later to patch the HTML injection vulnerability that allows arbitrary code execution through profile and document editing. Organizations running versions 17.0.0 through 17.4.2 should prioritize this update, as any authenticated user can exploit the {{/html}} injection flaw to execute Groovy and Python macros with full wiki access.

sudo dnf update python3

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST /bin/edit/.*\bprofile\b|POST /bin/save/.*content.*\b{{/html}}\b|groovy\.execute|python\.eval

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch.

Block HTTP POST requests containing {{/html}}, {{groovy}}, or {{python}} patterns in request bodies targeting /bin/edit, /bin/save, and profile endpoints; enforce strict input validation on wiki macro syntax before rendering.

How to check if you are affected

  1. Step 1: Run `python3 --version` to verify your installed Python version; this CVE affects XWiki Rendering on systems where Python is available for macro execution.
  2. Step 2: Check your XWiki installation with `grep -r 'version' /path/to/xwiki/WEB-INF/` or review the Administration panel to confirm if you're running XWiki Rendering 17.0.0–17.4.2.
  3. Step 3: Search application logs for patterns like `{{/html}}`, `groovy`, or `python` in profile edits and document modifications using `grep -i '{{/html\|groovy\|python' /var/log/xwiki/application.log | head -50`.
  4. Step 4: Verify the patch by checking the XWiki version in Administration > System Information; it should display 17.4.3 or later for the vulnerability to be resolved.

FAQ

What is CVE-2025-66474?

This vulnerability exploits insufficient input sanitization in XWiki Rendering's HTML handling, allowing authenticated users to inject {{/html}} tags that bypass security filters and execute arbitrary Groovy or Python macros with full system privileges.

Is CVE-2025-66474 being actively exploited?

No, CVE-2025-66474 is not currently listed on CISA's Known Exploited Vulnerabilities catalog, and no public exploits are widely available. However, the low barrier to entry (any authenticated user) makes proactive patching essential.

What versions of Python are affected by CVE-2025-66474?

XWiki Rendering versions 16.10.9 and below, 17.0.0 through 17.4.2, and 17.5.0-rc-1 through 17.5.0 are vulnerable; the fix is available in versions 16.10.10, 17.4.3, and 17.6.0-rc-1 and later.

How do I check if my server is vulnerable to CVE-2025-66474?

Run `curl http://your-xwiki-server/bin/view/Main/WebHome` and check the page source or admin console for the XWiki version number; if it falls between 17.0.0 and 17.4.2, your installation is vulnerable.

Does Defensia detect CVE-2025-66474?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Python is installed on a monitored server, CVE-2025-66474 will appear in your dashboard with remediation steps.

Related Python CVEs

CVE-2026-34938CVSS 10PraisonAI is a multi-agent teams system. Prior to version 1.5.90, execute_code() in praisonai-agents runs attacker-controlled Python inside a three-layer sandbox that can be fully bypassed by passing a str subclass with an overridden startswith() method to the _safe_getattr wrapper, achieving arbitrary OS command execution on the host. This issue has been patched in version 1.5.90.
CVE-2026-33054CVSS 10Mesop is a Python-based UI framework that allows users to build web applications. Versions 1.2.2 and below contain a Path Traversal vulnerability that allows any user supplying an untrusted state_token through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation. This vulnerability heavily exposes systems hosted utilizing FileStateSessionBackend. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds. This issue has been fixed in version 1.2.3.
CVE-2026-28505CVSS 10Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.0, the str_eval() function in notification_handler.py implements a sandboxed eval() for notification text templates. The sandbox attempts to restrict callable names by inspecting code.co_names of the compiled code object. However, co_names only contains names from the outer code object. When a lambda expression is used, it creates a nested code object whose attribute accesses are stored in code.co_consts, NOT in code.co_names. The sandbox never inspects nested code objects. This issue has been patched in version 2.17.0.
CVE-2026-25632CVSS 10EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water distribution networks. Prior to 0.16.1, EPyT-Flow’s REST API parses attacker-controlled JSON request bodies using a custom deserializer (my_load_from_json) that supports a type field. When type is present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-supplied arguments. This allows invoking dangerous classes such as subprocess.Popen, which can lead to OS command execution during JSON parsing. This also affects the loading of JSON files. This vulnerability is fixed in 0.16.1.
CVE-2026-8481CVSS 9.9IBM Langflow OSS 1.0.0 through 1.10.0 contain a critical remote code execution vulnerability in the code validation API endpoint. The POST /api/v1/validate/code endpoint accepts user-supplied Python code and executes it directly using Python's built-in exec() function without sandboxing, input validation, or privilege restrictions, enabling any authenticated user to execute arbitrary system commands with the full privileges of the Langflow server process.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-66474. Free for 1 server.

Get started free