Summary
Workarounds
Restricting edit rights on all existing App Within Minutes applications to trusted users mitigates at least the PoC exploit, but we can't exclude that there are other ways to exploit this vulnerability.
Impact
Any XWiki user with edit right on at least one App Within Minutes application (the default for all users XWiki) can obtain programming right/perform remote code execution by editing the application. The detailed reproduction steps can be found in the original bug report.
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
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.
Remediation advice
This vulnerability has been fixed in XWiki 17.0.0, 16.4.7, and 16.10.3.
Frequently Asked Questions
- What is CVE-2025-49586? CVE-2025-49586 is a high-severity incorrect authorization vulnerability in org.xwiki.platform:xwiki-platform-oldcore (maven), affecting versions >= 7.2-milestone-2, < 16.4.7. It is fixed in 16.4.7, 16.10.3, 17.0.0. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- Which versions of org.xwiki.platform:xwiki-platform-oldcore are affected by CVE-2025-49586? org.xwiki.platform:xwiki-platform-oldcore (maven) versions >= 7.2-milestone-2, < 16.4.7 is affected.
- Is there a fix for CVE-2025-49586? Yes. CVE-2025-49586 is fixed in 16.4.7, 16.10.3, 17.0.0. Upgrade to this version or later.
- Is CVE-2025-49586 exploitable, and should I be worried? Whether CVE-2025-49586 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-49586 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-49586?
- Upgrade
org.xwiki.platform:xwiki-platform-oldcoreto 16.4.7 or later - Upgrade
org.xwiki.platform:xwiki-platform-oldcoreto 16.10.3 or later - Upgrade
org.xwiki.platform:xwiki-platform-oldcoreto 17.0.0 or later
- Upgrade