CVE-2025-53837
CriticalCVSS 9.9Summary
XWiki Rendering prior to 14.10.2 and 15.0 RC1 allows any user who can edit their profile or any document to execute arbitrary script macros, including Groovy and Python, leading to remote code execution. The rendering output is included as HTML macro content without further escaping, allowing closure of the HTML macro and injection of script macros with programming rights.
Risk Assessment
An attacker can gain unrestricted read/write access to wiki content and execute arbitrary code.
Recommendation
Upgrade to 14.10.2 or 15.0 RC1, which prevent closing the HTML macro. If not possible, apply workaround by escaping rendering outputs.
Related vulnerabilities
- CVE-2026-93765Critical
Mongoid contains an unsafe reflection weakness in the document persistence layer. Passing keys from unauthenticated parties can trigger unintended internal method invocation instead of an array update, potentially causing deletion of stored records and unresponsiveness.
- CVE-2026-85497Critical
CareCam CM2507 IP cameras store the root password using a fixed legacy hash that is insufficiently resistant to offline cracking.
- CVE-2026-81321Critical
CM2507 IP cameras store wireless network credentials in cleartext within the device filesystem.
- CVE-2026-77240Critical
WACRM 0.7.0 and earlier has vulnerabilities: row-level security policies allow authenticated users to modify their own role and account ID, enabling privilege escalation and cross-tenant movement. Additionally, match_ai_knowledge_fts and match_ai_knowledge_semantic run as SECURITY DEFINER with no account membership check, allowing non-members to read another tenant's knowledge chunks.
- CVE-2026-84383Critical
libheif from 1.22.0 to 1.23.2 has a heap out-of-bounds write vulnerability. Crafted HEIF/HEIC/AVIF files with nested iden/auxl references cause duplicate Alpha planes with different bit depths, and scale_nearest_neighbor() allocates a buffer based on the first plane's 8-bit depth, leading to an overflow.
- CVE-2026-61682Critical
kcp before 0.31.4 and 0.32.2 fails to strip inbound identity headers (X-Remote-User, X-Remote-Group, X-Remote-Extra-*) before forwarding requests to shards. Any authenticated tenant can inject X-Remote-Group: system:masters, gaining full privileges.
- CVE-2026-10858Critical
IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 has a heap buffer underflow when processing multi-segment messages, which could allow an authenticated attacker to cause denial of service or arbitrary code execution.
- CVE-2026-10747Critical
IBM MQ Appliance has a heap buffer overflow in protocol message processing before authentication, allowing a remote attacker to cause DoS or potentially execute arbitrary code.
- CVE-2025-15399Critical
IBM Common Licensing Agent 9.0 and ART 9.0 (including subversions) are vulnerable to cross-site request forgery, allowing an attacker to execute malicious actions from a user that the website trusts.
- CVE-2026-93606Critical
A vulnerability in the vm2 library (npm) versions up to 3.12.0 allows sandbox escape in VM and NodeVM. When an embedder exposes a host API returning a host-realm Promise, the rejection sanitizer does not cover all cases, and sandboxed code can overwrite Promise properties to obtain an unsanitized host object. This can lead to arbitrary code execution on the host. Fixed in 3.12.1.
Original NVD description (English source)
XWiki Rendering is a generic rendering system that converts textual input in a given syntax (wiki syntax, HTML, etc) into another syntax (XHTML, etc). Prior to versions 14.10.2 and 15.0 RC1, 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 without further escaping and it is thus possible to close the HTML macro and inject script macros that are executed with programming rights. This has been patched in XWiki 14.10.2 and 15.0 RC1 by making sure that rendering output cannot close the surrounding HTML macro. A possible workaround is available. It is, in principle, possible to add escaping to all places where rendering output is used in wiki documents, but at the moment there is no list of them.