CVE-2022-1707 json
Google Tag Manager for WordPress <= 1.15 - Reflected Cross-Site Scripting via Site Search
published 2022-06-13 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-24991
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 89.3%
- EPSS 89.3% chance of exploitation in 30 days, percentile 99.7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- gtm4wp google_tag_manager 1.15.1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
89.28% chance of exploitation in the next 30 days, higher than 99.7% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Affected products
- duracelltomi GTM4WP – A Google Tag Manager (GTM) plugin for WordPress
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
wordfence.com
/threat-intel/vulnerabilities/id/0435ae14-c1fd-4611-acbe-5f3bafd4bb6a?source=cve
third-party-advisory
-
github.com
/duracelltomi/gtm4wp/issues/224
issue-tracking
-
github.com
/duracelltomi/gtm4wp/blob/1.15/public/frontend.php#L298
product
-
github.com
/duracelltomi/gtm4wp/blob/1.15/public/frontend.php#L782
product
-
wordfence.com
/vulnerability-advisories/#CVE-2022-1707
third-party-advisory
Sources
- CVE List CVE-2022-1707
- NVD CVE-2022-1707
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.