LiveActive security incident?Get immediate response
CVE Record

CVE-2022-1961: Google Tag Manager for WordPress (GTM4WP) <= 1.15.1 - Stored Cross-Site Scripting via Content Element ID

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.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-1961 is a stored cross-site scripting issue in the GTM4WP WordPress plugin through version 1.15.1. It matters mainly where administrators are not allowed to use unfiltered HTML. An admin-level user could save script content that later runs in site visitors' browsers.

Executive priority

Treat as a normal WordPress plugin maintenance issue unless untrusted administrators exist. Prioritize updating affected sites, but this is not supported as emergency active-exploitation work from the provided evidence.

Technical view

The flaw is insufficient escaping of the gtm4wp-options[scroller-contentid] setting in public/frontend.php. It is CWE-79 stored XSS with CVSS 3.1 score 5.5. The attack requires network access and high privileges, changes scope, and may affect confidentiality and integrity at low impact.

Likely exposure

Exposure is limited to WordPress sites using GTM4WP versions up to and including 1.15.1, especially multisite deployments or sites where unfiltered_html is disabled for administrators.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. A public technical reference is cited, but exploitation requires administrator access, which materially limits likely abuse scenarios.

Researcher notes

The key condition is administrative access combined with disabled unfiltered_html. Validate version and configuration before reporting exposure. Do not broaden impact to unauthenticated users or all administrators without additional evidence.

Mitigation direction

  • Inventory WordPress sites using the GTM4WP plugin.
  • Update GTM4WP beyond version 1.15.1 using vendor or WordPress.org guidance.
  • Restrict administrator accounts to trusted users only.
  • Review GTM4WP settings for unexpected script-like content.
  • Check vendor advisories before applying production changes.

Validation and detection

  • Confirm each site’s installed GTM4WP version.
  • Check whether WordPress multisite or unfiltered_html restrictions apply.
  • Review GTM4WP Content Element ID configuration for suspicious values.
  • Inspect admin audit logs for GTM4WP settings changes.
  • Verify the plugin changelog or changeset for the applied fix.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-1961 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-1961Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
duracelltomiGTM4WP – A Google Tag Manager (GTM) plugin for WordPress0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.