Summary
Workarounds
We're not aware of any workarounds.
Resources
Impact
The blog application in XWiki allowed remote code execution for any user who has edit right on any page. Normally, these are all logged-in users as they can edit their own user profile. To exploit, it is sufficient to add an object of type Blog.BlogPostClass to any page and to add some script macro with the exploit code to the "Content" field of that object.
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.
Remediation advice
The vulnerability has been patched in the blog application version 9.14 by executing the content of blog posts with the rights of the appropriate author.
Frequently Asked Questions
- What is CVE-2025-58365? CVE-2025-58365 is a high-severity code injection vulnerability in org.xwiki.contrib.blog:application-blog-ui (maven), affecting versions < 9.14. It is fixed in 9.14. Untrusted input is evaluated as executable code within the application's runtime environment.
- Which versions of org.xwiki.contrib.blog:application-blog-ui are affected by CVE-2025-58365? org.xwiki.contrib.blog:application-blog-ui (maven) versions < 9.14 is affected.
- Is there a fix for CVE-2025-58365? Yes. CVE-2025-58365 is fixed in 9.14. Upgrade to this version or later.
- Is CVE-2025-58365 exploitable, and should I be worried? Whether CVE-2025-58365 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-58365 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-58365? Upgrade
org.xwiki.contrib.blog:application-blog-uito 9.14 or later.