Quick answers
- Is CVE-2025-66024 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-66024 being exploited in the wild.
- How severe is CVE-2025-66024?
- Critical severity, with a CVSS score of 9, published 4 March 2026.
- Which products and versions are affected?
- org.xwiki.contrib.blog:application-blog-ui (Maven) < 9.15.7, >= 9.15, < 9.15.7, ECOSYSTEM:introduced=9.15,fixed=9.15.7; Xwiki Blog Application UI >= 9.15, < 9.15.7.
- Is there a fix for CVE-2025-66024?
- Yes. org.xwiki.contrib.blog:application-blog-ui (Maven): upgrade to 9.15.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-66024 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2025-66024?
- Check whether you run org.xwiki.contrib.blog:application-blog-ui (Maven), Xwiki Blog Application UI or Xwiki Blog Application at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- org.xwiki.contrib.blog:application-blog-ui (Maven): upgrade to 9.15.7 or later
# set org.xwiki.contrib.blog:application-blog-ui to 9.15.7 in your pom.xml or build.gradle
Technical details
A Stored Cross-Site Scripting (XSS) vulnerability exists in the XWiki Blog Application (org.xwiki.contrib.blog:application-blog-ui) due to improper neutralization of input during web page generation. The blog post title is injected directly into the HTML <title> tag without proper escaping. An attacker with 'create' or 'edit' permissions can inject a payload (e.g., </title><script>...) that executes JavaScript in the context of any user viewing the blog home page. This can lead to session hijacking or privilege escalation. The issue is fixed in version 9.15.7.
Affected products
- XWiki Blog Application UI >= 9.15, < 9.15.7
Identifiers
- CVE-2025-66024
- GHSA-h2xq-h7f9-vh6c
Timeline
- 2026-03-04: disclosed
- 2026-03-04: advisory
- 2026-03-04: patched