← Vulnerability feed

Vulnerability record · CVE-2022-1707 · published 13 June 2022

CVE-2022-1707: Google Tag Manager for WordPress plugin reflected XSS via s parameter

Gtm4wp · Google Tag Manager

The Google Tag Manager for WordPress plugin fails to sanitize the site search 's' parameter before populating it into the data layer, allowing reflected cross-site scripting in versions up to and including 1.15. Because the flaw sits in the public frontend, any site visitor can be targeted, and successful exploitation runs script in the victim's browser under the site's origin.

6.1 CVSS 3.1 Medium EPSS 89% · top 0.2% CWE-79 · Cross-site scripting
6.1CVSS 3.1 base score, v2 4.3
89%EPSS exploitation probability, 30 days
NoNot in CISA KEV
1Affected product versions listed by NVD
10References
17 Jun 2026Last modified by NVD

Description

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.

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

Automated analysis

Generated by VULONE's analysis model from the NVD record, CISA KEV and EPSS data on 18 September 2026. Confidence: high.

high priorityUnauthenticated reflected XSS with a very high EPSS score and broad WordPress exposure warrants prompt patching despite the medium CVSS rating.

What it is

The Google Tag Manager for WordPress plugin fails to sanitize the site search 's' parameter before populating it into the data layer, allowing reflected cross-site scripting in versions up to and including 1.15. Because the flaw sits in the public frontend, any site visitor can be targeted, and successful exploitation runs script in the victim's browser under the site's origin.

Impact

An attacker can execute arbitrary JavaScript in a victim's browser in the context of the affected WordPress site, enabling session theft, credential phishing, or redirection to malicious content.

Attack surface

Reached over the network through the site search parameter, which is reflected into the data layer on public pages. No authentication is required, but the victim must be induced to click a crafted link (UI:R).

Exploitation

Not listed in CISA KEV and no public exploit references are tagged in the record, but EPSS is very high (0.89276, 99.77th percentile), indicating elevated likelihood of exploitation activity.

What to do

  • Update the Google Tag Manager for WordPress plugin to a version later than 1.15.
  • If immediate patching is not possible, disable or restrict the plugin until it can be updated.
  • Deploy a WAF rule to block script payloads in the 's' search parameter.
  • Sanitize and encode the search parameter before it is written into the data layer.
  • Review site search and data layer output for other unsanitized reflected inputs.

Detection

  • Search web server and WAF logs for script tags or event handlers in the 's' query parameter.
  • Monitor for requests containing encoded JavaScript in search URLs hitting frontend.php.
  • Alert on anomalous outbound redirects or script loads originating from search result pages.
  • Review plugin version inventory to identify sites still running 1.15 or earlier.

This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.

Affected products

1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.

References

Track CVE-2022-1707 inside VULONE

Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.

Start free Open in platform

Related vulnerabilities

Same products first, then exploited flaws of the same weakness class.

4.8CVE-2022-1961Gtm4wp google tag manager cross-site scripting vulnerabilityThe Google Tag Manager for WordPress (GTM4WP) plugin is vulnerable to Stored Cross-Site Scripting due to insufficient escaping via the `gtm4wp-option…EPSS 1.1%6.1CVE-2026-42897Microsoft Exchange Server XSS enables spoofingMicrosoft Exchange Server and Exchange Server Subscription Edition fail to neutralize input during web page generation, a cross-site scripting flaw (…KEVEPSS 0.52%analysed6.1CVE-2025-48700Zimbra Classic UI stored XSS via crafted email HTMLZimbra Collaboration Suite Classic UI fails to properly sanitize HTML content in email messages, allowing crafted tag structures and attribute values…KEVEPSS 1.7%analysed6.1CVE-2025-66376Zimbra Collaboration Classic UI stored XSS via CSS @import in emailZimbra Collaboration Suite 10 before 10.0.18 and 10.1 before 10.1.13 allows stored cross-site scripting in the Classic UI through CSS @import directi…KEVEPSS 20%analysed6.1CVE-2025-68461Roundcube Webmail XSS via SVG animate tagRoundcube Webmail before 1.5.12 and 1.6 before 1.6.12 is vulnerable to cross-site scripting through the animate tag in an SVG document. Because the f…KEVEPSS 27%analysed10.0CVE-2026-22769Dell RecoverPoint for Virtual Machines hardcoded credential flawDell RecoverPoint for Virtual Machines versions prior to 6.0.3.1 HF1 contain a hardcoded credential vulnerability (CWE-798). An unauthenticated remot…KEVEPSS 13%analysed7.1CVE-2025-14611Gladinet CentreStack and Triofox hardcoded AES key enables file inclusionCentreStack and Triofox before 16.12.10420.56791 use hardcoded values in their AES cryptoscheme, weakening protection for publicly exposed endpoints.…KEVEPSS 53%analysed5.4CVE-2021-26829OpenPLC ScadaBR stored XSS via system_settings.shtmOpenPLC ScadaBR through 0.9.1 on Linux and through 1.12.4 on Windows allows stored cross-site scripting through system_settings.shtm. Because the inj…KEVEPSS 48%analysed

Source: NIST National Vulnerability Database (record CVE-2022-1707), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.