Cross-Site Scripting (XSS) in @apostrophecms/seo (CVE-2026-53608)
Summary
Cross-site scripting in @apostrophecms/seo (CVE-2026-53608). Confidential information can be exposed externally. Exploitable via seoGoogleTrackingId. Mitigation: upgrade to 1.5.0 or later.
Original description
The description as published by the source.
ApostropheCMS is an open-source Node.js content management system. Versions up to and including 1.4.2 of the @apostrophecms/seo package injects the Google Analytics Tracking ID (seoGoogleTrackingId) and Google Tag Manager ID (seoGoogleTagManager) directly into `` tag bodies using JavaScript template literals without any sanitization or validation. Any user with editor-level access (the default role for content managers) can set these fields to a malicious value, resulting in stored XSS that executes on every page for every visitor of the site. As of time of publication, no known patched versions are available.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53608 has been found in @apostrophecms/seo.
Attackers can target a specific entry point like seoGoogleTrackingId over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade @apostrophecms/seo to 1.5.0 or later.
If unsure, ask your IT team or search "@apostrophecms/seo CVE-2026-53608" on the vendor's site.
CVE-2026-53608 (@apostrophecms/seo) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: seoGoogleTrackingId / seoGoogleTagManager / _id
Patched: 1.5.0 — apply immediately
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.
Cross-site scripting (XSS) (CWE-79) exists in @apostrophecms/seo. Attackers reach the vulnerable code path via seoGoogleTrackingId.
Check the vendor advisory for the affected versions of @apostrophecms/seo. Attack surface: seoGoogleTrackingId / seoGoogleTagManager / _id.
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.
Update to 1.5.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@apostrophecms/seo' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@apostrophecms/seo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@apostrophecms/seoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @apostrophecms/seo to 1.5.0ステージング環境で 1.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com