CVE-2022-1961 - Google Tag Manager Plugin
CVE-2022-1961
The Google Tag Manager for WordPress (GTM4WP) plugin is vulnerable to Stored Cross-Site Scripting due to insufficient escaping via the `gtm4wp-options[scroller-contentid]` parameter found in the `~/public/frontend.php` file which allowed attackers with administrative user access to inject arbitrary web scripts, in versions up to and including 1.15.1. This affects multi-site installations where unfiltered_html is disabled for administrators, and sites where unfiltered_html is disabled.
CVE-2022-1961
MEDIUM
CVSS 5.5
Published 2022-06-13
Updated 2025-05-05
AI Risk High (76/100)
Active Exploit: Likely
Published Exploit: Public exploit references found
Priority: P2 Urgent
Severity Band
MEDIUM
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
Affected Components
1
Reference Links
5
AI Risk Engine
High (76/100)
Exploitability
High
Active Exploitation
Likely
Published Exploit Status
Public exploit references found
AI Context
Machine-generated threat intelligence
AI
Updated 110 days ago
AI enriched 110 days ago (2026-04-12 03:09 UTC)
Technical Summary
The Google Tag Manager for WordPress (GTM4WP) plugin is vulnerable to Stored Cross-Site Scripting due to insufficient escaping via the `gtm4wp-options[scroller-contentid]` parameter found in the `~/public/frontend.php` file which allowed attackers with administrative user access to inject arbitrary web scripts, in versions up to and including 1.15.1. This affects multi-site installations where unfiltered_html is disabled for administrators, and sites where unfiltered_html is disabled.
Potential Impact
Severity is MEDIUM (CVSS 5.5). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.
Exploitability Assessment
Exploitability is assessed as High based on published exploit references, remote code execution potential.
Primary risk drivers: published exploit references, remote code execution potential
Mitigation Recommendations
Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.
Detection & Monitoring
Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.
Business Impact Lens
AI risk score 76/100 (High, High) with priority P2 Urgent. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.