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

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

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

Q: Is CVE-2022-1961 being exploited?

CVE-2022-1961 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-1961 affect?

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

Q: How urgent is CVE-2022-1961?

Priority 41/100. Public exploit reference

This month

MEDIUM 5.5UPGRADE

CVE-2022-1961 is a medium-severity flaw (CVSS 5.5) 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 (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 s

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	1.1% (top 34%)
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 14:15 UTCPublished CVE record published
2026-06-17 04:23 UTCUpdated Record last modified

gtm4wp google tag manager UPGRADE

Affected: < 1.15.2

Fixed in: 1.15.2

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.2 (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-1961?

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

Is CVE-2022-1961 being exploited?

CVE-2022-1961 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-1961 affect?

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

How urgent is CVE-2022-1961?

Priority 41/100. Public exploit reference

Software pages

WordPress vulnerabilities · PHP vulnerabilities

Related CVEs

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

References

← Back to latest CVEs