{"answers":{"affected":"2 open source packages ship an affected version, including org.xwiki.rendering:xwiki-rendering-xml.","exploited":"There is no known exploitation of CVE-2025-53837 in the wild and no public exploit code.","fix":"Upgrade org.xwiki.rendering:xwiki-rendering-xml to 14.10.2 or later.","what":"CVE-2025-53837 is a critical code injection vulnerability in xwiki-rendering, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-53837 and fix it if it is affected.\n\nWhat it is: CVE-2025-53837 is a critical code injection vulnerability in xwiki-rendering, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-53837 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.xwiki.rendering:xwiki-rendering-xml (Maven): affected all versions; fixed in 14.10.2\n- org.xwiki.rendering:xwiki-rendering-xml (Maven): affected all versions; fixed in 14.10.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-53837/ (Markdown: https://insights.sbomify.com/CVE-2025-53837/index.md)","id":"CVE-2025-53837","markdown":"https://insights.sbomify.com/CVE-2025-53837/index.md","name":"CVE-2025-53837","record":{"aliases":["GHSA-26vp-8gxg-v4pg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"XWiki rendering library","requires_auth":"low_privilege","summary":"Attackers can inject script macros via rendering output to execute arbitrary code and access wiki contents in XWiki.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-95","name":"Improper Neutralization of Directives in Dynamically Evaluated Code"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"org.xwiki.rendering:xwiki-rendering-xml has an Eval Injection issue","id":"CVE-2025-53837","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":2,"n_references":7,"next":{"headline":"LinkAce has a Stored One Click XSS vulnerability","id":"CVE-2025-53838"},"packages":[{"ecosystem":"Maven","fixed":["14.10.2"],"introduced":["0"],"last_affected":[],"package":"org.xwiki.rendering:xwiki-rendering-xml","purl":null,"source":"GHSA-26vp-8gxg-v4pg"},{"ecosystem":"Maven","fixed":["14.10.2"],"introduced":["0"],"last_affected":[],"package":"org.xwiki.rendering:xwiki-rendering-xml","purl":"pkg:maven/org.xwiki.rendering/xwiki-rendering-xml","source":"GHSA-26vp-8gxg-v4pg"}],"prev":{"headline":"XWiki Rendering is vulnerable to RCE attacks when processing nested macros","id":"CVE-2025-53836"},"products":["xwiki-rendering"],"published":"2026-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["xwiki"]},"summary":"Attackers can inject script macros via rendering output to execute arbitrary code and access wiki contents in XWiki.","url":"https://insights.sbomify.com/CVE-2025-53837/"}