CVE-2025-66024

Workarounds

XWiki Blog Application maintainers are not aware of any workarounds.

Resources

• https://jira.xwiki.org/browse/BLOG-245
• https://github.com/xwiki-contrib/application-blog/commit/cca87f0a0edc2e7e049d46d51f4a4d8f78b714ba

Attribution

Łukasz Rybak reported this vulnerability.

The Blog Application is vulnerable to Stored Cross-Site Scripting (XSS) via the Blog Post Title. The vulnerability arises because the post title is injected directly into the HTML tag without proper escaping.

An attacker with permissions to create or edit blog posts can inject malicious JavaScript into the title field. This script will execute in the browser of any user (including administrators) who views the blog post. This leads to potential session hijacking or privilege escalation.

To reproduce:

• Log in as a user with rights to create blog posts.
• Create a new blog post.
• In the Title field, insert the following payload designed to break out of the title tag: </title><script>alert('XSS in title blog')</script>
• Save (Publish) the post.
• View the post in the blog home page

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2025-66024 has a CVSS score of 9.0 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.15.7); upgrading removes the vulnerable code path.

Kodem intelligence

The vulnerability has been patched in the blog application version 9.15.7 by adding missing escaping.

1. What is CVE-2025-66024? CVE-2025-66024 is a high-severity cross-site scripting (XSS) vulnerability in org.xwiki.contrib.blog:application-blog-ui (maven), affecting versions < 9.15.7. It is fixed in 9.15.7. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2025-66024? CVE-2025-66024 has a CVSS score of 9.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.xwiki.contrib.blog:application-blog-ui are affected by CVE-2025-66024? org.xwiki.contrib.blog:application-blog-ui (maven) versions < 9.15.7 is affected.
4. Is there a fix for CVE-2025-66024? Yes. CVE-2025-66024 is fixed in 9.15.7. Upgrade to this version or later.
5. Is CVE-2025-66024 exploitable, and should I be worried? Whether CVE-2025-66024 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
6. What actually determines whether CVE-2025-66024 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.
7. How do I fix CVE-2025-66024? Upgrade org.xwiki.contrib.blog:application-blog-ui to 9.15.7 or later.