LiveActive security incident?Get immediate response
CVE Record

CVE-2022-1707: Google Tag Manager for WordPress <= 1.15 - Reflected Cross-Site Scripting via Site Search

The Google Tag Manager for WordPress plugin for WordPress is vulnerable to reflected Cross-Site Scripting via the s parameter due to the site search populating into the data layer of sites with insufficient sanitization in versions up to an including 1.15. The affected file is ~/public/frontend.php and this could be exploited by unauthenticated attackers.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects the Google Tag Manager for WordPress plugin through version 1.15. A search term could be reflected into the page’s data layer without enough sanitization, enabling cross-site scripting if a user follows a crafted link. The bundle does not show active exploitation.

Executive priority

Treat as a medium-priority web exposure issue. It is not a server takeover by itself, but successful exploitation could affect user trust, session security, or site integrity for visitors who open crafted links.

Technical view

CVE-2022-1707 is reflected XSS in GTM4WP via the WordPress site search s parameter. The vulnerable handling is described in public/frontend.php, where site search data is populated into the GTM data layer with insufficient sanitization. It is unauthenticated but requires user interaction, matching CVSS 6.1.

Likely exposure

Public WordPress sites running GTM4WP version 1.15 or earlier are the likely exposure. Risk is higher where site search is enabled and users can be induced to open attacker-controlled search URLs.

Exploitation context

The source bundle describes unauthenticated reflected XSS requiring user interaction. CISA KEV status is false, and no provided source establishes active exploitation in the wild.

Researcher notes

Focus validation on GTM4WP <=1.15 and the site-search data-layer path in public/frontend.php. Evidence is sufficient for affected scope and vulnerability class, but the bundle does not provide exploit prevalence, active exploitation, or an exact fixed-version number.

Mitigation direction

  • Inventory WordPress sites using GTM4WP.
  • Upgrade GTM4WP to a vendor-supported version newer than 1.15 where available.
  • If upgrade is unavailable, disable or remove the plugin until vendor guidance is clear.
  • Review vendor and Wordfence guidance for the confirmed fixed release.
  • Apply normal XSS hardening controls at the edge where available.

Validation and detection

  • Confirm installed GTM4WP versions across managed WordPress sites.
  • Check whether affected sites expose WordPress search functionality.
  • Review the plugin changelog or vendor issue for the fixed release.
  • Verify search input is safely encoded in rendered pages after remediation.
  • Review web logs for unusual search-parameter probing.
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-1707 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
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
5Source 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
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.