← Back
CVE-2025-66024
critical
CVSS 9.0
Cross-Site Scripting (XSS) in org.xwiki.contrib.blog:application-blog-ui (CVE-2025-66024)
Summary
cross-site scripting in org.xwiki.contrib.blog:application-blog-ui (CVE-2025-66024). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `9.15.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-66024** has been found in org.xwiki.contrib.blog:application-blog-ui.
Successful exploitation can lead to full system takeover. CVSS score: 9.0/10.
What to do: upgrade org.xwiki.contrib.blog:application-blog-ui to **9.15.7** or later.
If unsure, ask your IT team or search "org.xwiki.contrib.blog:application-blog-ui CVE-2025-66024" on the vendor's site.
CVE-2025-66024 (org.xwiki.contrib.blog:application-blog-ui) — CWE-79 / CVSS v3 9.0
Attack vector: remote (network-reachable)
Patched: `9.15.7` — apply immediately
Workaround: We're not aware of any workarounds.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in org.xwiki.contrib.blog:application-blog-ui.
📍 Affected scope
org.xwiki.contrib.blog:application-blog-ui — .
🔥 Severity
Severity: Critical (CVSS 9.0/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **9.15.7**.
🛡️ Workaround
Workaround: We're not aware of any workarounds.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.xwiki.contrib.blog:application-blog-ui' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.xwiki.contrib.blog:application-blog-ui' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.xwiki.contrib.blog:application-blog-ui` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
We're not aware of any workarounds.パッチが適用されるまでの応急処置として、We're not aware of any workarounds. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade org.xwiki.contrib.blog:application-blog-ui to 9.15.7ステージング環境で 9.15.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.xwiki.contrib.blog:application-blog-ui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.15.7"}]}]