How severe is CVE-2025-66024?

No CVSS score has been assigned to CVE-2025-66024 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-66024?

CVE-2025-66024 affects the following packages: org.xwiki.contrib.blog:application-blog-ui (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-66024?

Update org.xwiki.contrib.blog:application-blog-ui to 9.15.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-66024 is resolved across your whole dependency graph.

How do I detect CVE-2025-66024 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.contrib.blog:application-blog-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-66024 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2025-66024 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-66024 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-66024?

CVE-2025-66024 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-66024?

CVE-2025-66024 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-66024 published, and has it been updated?

CVE-2025-66024 was published on March 4, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2025-66024 — application-blog-ui

Fix: xwiki-contrib/application-blog@cca87f0

CVE-2025-66024 is a Cross-site Scripting (XSS) vulnerability in org.xwiki.contrib.blog:application-blog-ui. A fix is available for org.xwiki.contrib.blog:application-blog-ui — see the affected versions and patch details below.

XWiki Blog Application home page vulnerable to Stored XSS via Post Title

Also known asGHSA-h2xq-h7f9-vh6c

Published

Mar 4, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-66024.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.07%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.xwiki.contrib.blog:application-blog-ui

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

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 <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.

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

Patches

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

Workarounds

We're not aware of any workarounds.

References

Attribution

Łukasz Rybak reported this vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.contrib.blog:application-blog-ui`	≥ 9.15&&< 9.15.7	9.15.7`org.xwiki.contrib.blog:application-blog-ui:9.15.7`

Affected Products

1 product · 1 configurations

Application

blog applicationxwiki

< 9.15.7

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.contrib.blog:application-blog-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.contrib.blog:application-blog-ui to 9.15.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-66024 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact 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 `<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. To reproduce: * Log in as a user with rights to create blog posts. * Create a new b

O3 Security · Impact-Aware SCA

Is CVE-2025-66024 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works