HomeWordPress vulnerabilitiesGTM4WP
GTM4WP vulnerabilities
GTM4WP has 2 known vulnerabilities in this database. The most recent published record is dated 29 Jul 2026.
- Known vulnerabilities
- 2
- Active installs
- 700,000+
- Latest version
- 2.0.4
- Last updated
- 29 Sep 2026
- Most recent
- 29 Jul 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-16597 | High 7.2 | Up to 1.22.3 | Fixed in a later version (latest 2.0.4) | 29 Jul 2026 |
| Cross-site scripting (XSS) CVE-2022-1961 | Medium 5.5 | Before 1.15.2 | Fixed in 1.15.2 | 13 Jun 2022 |
Read the published descriptions
- CVE-2026-16597, 29 Jul 2026
- The GTM4WP - A Google Tag Manager (GTM) plugin for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via WooCommerce Billing Fields in all versions up to, and including, 1.22.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the GTM4WP WooCommerce order data integration option (GTM4WP_OPTION_INTEGRATE_WCORDERDATA) to be enabled, and is exploited by placing a guest checkout order with a JavaScript payload in a WooCommerce billing field such as the billing first name. CVE record
- CVE-2022-1961, 13 Jun 2022
- 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 sites where unfiltered_html is disabled. CVE record
What to do if you run GTM4WP
If you run GTM4WP, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new GTM4WP vulnerabilities
Free. We email you when a new vulnerability is published for GTM4WP, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.