Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Plugin security history

GTM4WP – A Google Tag Manager (GTM) plugin for WordPress Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 4 vulnerability records associated with GTM4WP – A Google Tag Manager (GTM) plugin for WordPress, published between 2022 and 2026.

Dataset last synchronized: 2026-08-03 00:31:25 UTC

At a glance

Security Snapshot

4Total records
0Critical
2High
2Medium
0Low
0Informational
4Patched records
0Currently marked unpatched
2022-05-12First disclosure
2026-07-28Latest disclosure
3 of 4CVE coverage

Year-by-Year Timeline

YearRecordsRelative volume
202233 records
202611 records

Severity Breakdown

SeverityRecordsShare
High250%
Medium250%

Vulnerability-Type Breakdown

Cross-Site Scripting

4 records100%

First: 2022. Latest: 2026.

Patch Status

Patched
4
Currently marked unpatched
0
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

  • 1.22.4
  • 1.15.2
  • 1.15.1

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-1.22.3GTM4WP <= 1.22.3 - Unauthenticated Stored Cross-Site Scripting via WooCommerce Billing FieldsJuly 28, 20261.22.4High
*-1.15.1Google Tag Manager for WordPress (GTM4WP) <= 1.15.1 - Stored Cross-Site Scripting via Content Element IDMay 31, 20221.15.2Medium
*-1.15Google Tag Manager for WordPress <= 1.15 - Reflected Cross-Site Scripting via Site SearchMay 19, 20221.15.1Medium
*-1.15Google Tag Manager for WordPress <= 1.15 - Cross-Site Scripting via Cloudflare Country CodeMay 12, 20221.15.1High

Selected source records

Latest Records

HighCVE-2026-16597

GTM4WP <= 1.22.3 - Unauthenticated Stored Cross-Site Scripting via WooCommerce Billing Fields

Published: July 28, 2026

Affected versions
*-1.22.3
Patched versions
1.22.4
Original Wordfence record
MediumCVE-2022-1961

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

Published: May 31, 2022

Affected versions
*-1.15.1
Patched versions
1.15.2
Original Wordfence record
MediumCVE-2022-1707

Google Tag Manager for WordPress <= 1.15 - Reflected Cross-Site Scripting via Site Search

Published: May 19, 2022

Affected versions
*-1.15
Patched versions
1.15.1
Original Wordfence record
High

Google Tag Manager for WordPress <= 1.15 - Cross-Site Scripting via Cloudflare Country Code

Published: May 12, 2022

Affected versions
*-1.15
Patched versions
1.15.1
Original Wordfence record

Highest-Severity Records

HighCVE-2026-16597

GTM4WP <= 1.22.3 - Unauthenticated Stored Cross-Site Scripting via WooCommerce Billing Fields

Published: July 28, 2026

Affected versions
*-1.22.3
Patched versions
1.22.4
Original Wordfence record
High

Google Tag Manager for WordPress <= 1.15 - Cross-Site Scripting via Cloudflare Country Code

Published: May 12, 2022

Affected versions
*-1.15
Patched versions
1.15.1
Original Wordfence record
MediumCVE-2022-1707

Google Tag Manager for WordPress <= 1.15 - Reflected Cross-Site Scripting via Site Search

Published: May 19, 2022

Affected versions
*-1.15
Patched versions
1.15.1
Original Wordfence record
MediumCVE-2022-1961

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

Published: May 31, 2022

Affected versions
*-1.15.1
Patched versions
1.15.2
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.

Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.

Data Source, Attribution and Methodology

This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.

Return to the Security History Directory