Skip to main content
Mallory
High

Stored XSS in ApostropheCMS @apostrophecms/seo

IdentifiersCVE-2026-53608CWE-79· Improper Neutralization of Input…

CVE-2026-53608 is a stored cross-site scripting vulnerability in the @apostrophecms/seo package for ApostropheCMS affecting versions up to and including 1.4.2. The package injects the Google Analytics Tracking ID (seoGoogleTrackingId) and Google Tag Manager ID (seoGoogleTagManager) directly into <script> tag bodies using JavaScript template literals without sanitization or validation. Because these values are rendered into executable script context, an attacker with editor-level access can supply a malicious payload that is stored by the CMS and executed in visitors' browsers whenever pages are viewed. The issue affects site-wide rendered pages where the vulnerable SEO configuration is included.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in persistent client-side code execution in the browsers of users visiting the affected site. Because the payload executes on every page for every visitor, an attacker can steal session data, perform actions on behalf of authenticated users, modify page content, inject additional malicious JavaScript, and compromise confidentiality and integrity within the web application context. The provided CVSS v3.1 vector indicates changed scope with high confidentiality and integrity impact and no direct availability impact.

Mitigation

If you can’t patch tonight, do this now.

Until a patch is available, restrict access to the affected SEO settings to fully trusted administrators only and remove editor-level ability to modify seoGoogleTrackingId and seoGoogleTagManager. Audit existing values for both settings and replace any unexpected or nonconforming content. If possible, disable the vulnerable analytics/tag-manager injection functionality entirely. Deploy a restrictive Content Security Policy to reduce XSS impact, recognizing that CSP may not fully mitigate inline script execution depending on current site configuration.

Remediation

Patch, then assume compromise.

Upgrade to a vendor-fixed release once one becomes available. At the time of publication, no known patched version was available. The vulnerable behavior must be corrected by ensuring seoGoogleTrackingId and seoGoogleTagManager are not inserted into script bodies without strict validation and context-appropriate escaping. These fields should be constrained to expected identifier formats for Google Analytics and Google Tag Manager values rather than allowing arbitrary input.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.