CVE-2025-66024: XWiki Blog Application home page vulnerable to Stored XSS via Post Title
The XWiki blog application allows users of the XWiki platform to create and manage blog posts. Versions starting with 9.15 and prior to 9.15.7 are 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 <title> 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. The vulnerability has been patched in the blog application version 9.15.7 by adding missing escaping. No known workarounds are available.
Security readout for executives and security teams
Plain-English summary
A user allowed to create or edit XWiki blog posts can place malicious script content in a post title. When another user, including an administrator, views the post, the script can run in their browser, potentially enabling session theft or privilege escalation.
Executive priority
Treat remediation as high priority, especially on externally reachable or broadly authored XWiki deployments. Upgrade promptly and review authoring permissions. Immediate emergency response is not supported solely by the supplied evidence because active exploitation has not been reported.
Technical view
CVE-2025-66024 is a stored cross-site scripting vulnerability in xwiki-contrib application-blog-ui versions 9.15 through 9.15.6. Blog post titles were inserted into the HTML title element without proper escaping. Version 9.15.7 adds the missing escaping. The supplied CVSS 4.0 score is 8.6.
Likely exposure
Exposure requires an affected Blog Application version and an account permitted to create or edit blog posts. Risk increases where untrusted or lower-privileged users have those permissions and administrators view their posts. The supplied sources do not establish how widely affected versions are deployed.
Exploitation context
The attack is network-accessible, low-complexity, and requires low privileges plus a victim viewing the affected post. Stored content can affect multiple viewers. The source bundle reports no CISA KEV listing and provides no evidence of active exploitation in the wild.
Researcher notes
The vulnerable sink is the blog post title rendered inside the HTML title element without escaping. The relevant weakness is CWE-79. Impact depends on attacker authoring privileges and victim interaction. Vendor commits document the escaping change, but the supplied evidence does not demonstrate public exploitation.
Mitigation direction
Upgrade the XWiki Blog Application to version 9.15.7 or later.
Prioritize systems where untrusted users can create or edit blog posts.
Restrict blog authoring permissions until the upgrade is complete.
Follow vendor guidance because no workaround is documented.
Validation and detection
Inventory installed Blog Application versions and identify releases from 9.15 through 9.15.6.
Review which accounts and groups can create or edit blog posts.
Inspect existing post titles for unexpected HTML or script-like content.
After upgrading, confirm the application reports version 9.15.7 or later.
Verify post titles are safely escaped in rendered page titles.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.