CVE-2022-1707: The Google Tag Manager for WordPress plugin for WordPress is vulnerable to reflected Cross-Site Scripting via

Q: How do I fix CVE-2022-1707?

google tag manager: upgrade to 1.15.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-1707 being exploited?

CVE-2022-1707 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-1707 affect?

CVE-2022-1707 affects google tag manager. Severity is medium (CVSS 6.1). 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

Q: How urgent is CVE-2022-1707?

Priority 46/100. EPSS top 1%: very likely to be exploited

This week

MEDIUM 6.1UPGRADE

CVE-2022-1707 is a medium-severity flaw (CVSS 6.1) affecting google tag manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

EPSS top 1%: very likely to be exploited

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	89.3% (top 1%)
CISA exploited list	No
Weakness	CWE-79
Published	2022-06-13
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: gtm4wp

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-06-13 13:15 UTCPublished CVE record published
2026-06-17 04:22 UTCUpdated Record last modified

gtm4wp google tag manager UPGRADE

Affected: < 1.15.1

Fixed in: 1.15.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy google-tag-manager || rpm -q google-tag-manager || google-tag-manager --version

2. UPGRADE to 1.15.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade google-tag-manager

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade google-tag-manager

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-1707?

google tag manager: upgrade to 1.15.1. Exact commands for each OS are on this page.

Is CVE-2022-1707 being exploited?

CVE-2022-1707 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-1707 affect?

CVE-2022-1707 affects google tag manager. Severity is medium (CVSS 6.1). 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

How urgent is CVE-2022-1707?

Priority 46/100. EPSS top 1%: very likely to be exploited

Software pages

WordPress vulnerabilities · PHP vulnerabilities

Related CVEs

CVE-2022-1961 MEDIUM 5.5 UPGRADE The Google Tag Manager for WordPress (GTM4WP) plugin is vulnerable to Stored Cross-Site Scripting due to insuf

References

← Back to latest CVEs