Summary
XWiki allows remote code execution through default value of wiki macro wiki-type parameters
Workarounds
We're not aware of any workarounds except for upgrading.
Impact
Any user with edit right on a page (could be the user's profile) can execute code (Groovy, Python, Velocity) with programming right by defining a wiki macro. This allows full access to the whole XWiki installation and thus impacts its confidentiality, integrity and availability. The main problem is that if a wiki macro parameter allows wiki syntax, its default value is executed with the rights of the author of the document where it is used. This can be exploited by overriding a macro like the children macro that is used in a page that has programming right like the page XWiki.ChildrenMacro and thus allows arbitrary script macros. The full reproduction steps can be found in the original issue.
Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This vulnerability has been patched in XWiki 16.4.7, 16.10.3 and 17.0.0 by executing wiki parameters with the rights of the wiki macro's author when the parameter's value is the default value.
Frequently Asked Questions
- What is CVE-2025-49581? CVE-2025-49581 is a high-severity code injection vulnerability in org.xwiki.platform:xwiki-platform-rendering-wikimacro-store (maven), affecting versions >= 11.10.11, < 12.0. It is fixed in 16.4.7, 16.10.3, 17.0.0. Untrusted input is evaluated as executable code within the application's runtime environment.
- Which versions of org.xwiki.platform:xwiki-platform-rendering-wikimacro-store are affected by CVE-2025-49581? org.xwiki.platform:xwiki-platform-rendering-wikimacro-store (maven) versions >= 11.10.11, < 12.0 is affected.
- Is there a fix for CVE-2025-49581? Yes. CVE-2025-49581 is fixed in 16.4.7, 16.10.3, 17.0.0. Upgrade to this version or later.
- Is CVE-2025-49581 exploitable, and should I be worried? Whether CVE-2025-49581 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-49581 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-49581?
- Upgrade
org.xwiki.platform:xwiki-platform-rendering-wikimacro-storeto 16.4.7 or later - Upgrade
org.xwiki.platform:xwiki-platform-rendering-wikimacro-storeto 16.10.3 or later - Upgrade
org.xwiki.platform:xwiki-platform-rendering-wikimacro-storeto 17.0.0 or later
- Upgrade