CVE-2022-1961
Last modified
CVE-2022-1961 is a medium-severity vulnerability rated 4.8/10 on the CVSS scale. 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.. EPSS estimates a 1.05% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Gtm4wp | Google Tag Manager | < 1.15.2 |
References
- https://gist.github.com/Xib3rR4dAr/02a21cd0ea0b7bf586131c5eebb69f1dExploit, Third Party Advisory
- https://wordpress.org/plugins/duracelltomi-google-tag-manager/#developersProduct, Release Notes
- https://www.wordfence.com/vulnerability-advisories/#CVE-2022-1961Third Party Advisory
- https://gist.github.com/Xib3rR4dAr/02a21cd0ea0b7bf586131c5eebb69f1dExploit, Third Party Advisory
- https://wordpress.org/plugins/duracelltomi-google-tag-manager/#developersProduct, Release Notes
- https://www.wordfence.com/vulnerability-advisories/#CVE-2022-1961Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-1961?
How severe is CVE-2022-1961?
How do I fix CVE-2022-1961?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-1955Session 1.13.0 allows an attacker with physical access to th…4.6
- CVE-2022-1956The Shortcut Macros WordPress plugin through 1.3 does not ha…4.3
- CVE-2022-1957The Comment License WordPress plugin before 1.4.0 does not h…4.3
- CVE-2022-1958A vulnerability classified as critical has been found in Fil…6.5
- CVE-2022-1959AppLock version 7.9.29 allows an attacker with physical acce…6.6
- CVE-2022-1960The MyCSS WordPress plugin through 1.1 does not have CSRF ch…4.3
- CVE-2022-1962Uncontrolled recursion in the Parse functions in go/parser b…5.5
- CVE-2022-1963An issue has been discovered in GitLab CE/EE affecting all v…5.3
- CVE-2022-1964The Easy SVG Support WordPress plugin before 3.3.0 does not …5.4
- CVE-2022-1965Multiple products of CODESYS implement a improper error hand…8.1
- CVE-2022-1966Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2022-1967The WP Championship WordPress plugin before 9.3 is lacking C…6.5
Are you affected by CVE-2022-1961?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
