Summaryinfo

A vulnerability, which was classified as problematic, has been found in Google Tag Manager Plugin up to 1.15.1 on WordPress. Affected by this issue is some unknown functionality of the file ~/public/frontend.php. The manipulation of the argument gtm4wp-options[scroller-contentid] leads to cross site scripting. This vulnerability is handled as CVE-2022-1961. The attack may be launched remotely. There is no exploit available. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Detailsinfo

A vulnerability classified as problematic was found in Google Tag Manager Plugin up to 1.15.1 on WordPress (WordPress Plugin). Affected by this vulnerability is an unknown part of the file ~/public/frontend.php. The manipulation of the argument gtm4wp-options[scroller-contentid] with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. The summary by CVE is:

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.

The weakness was presented 06/13/2022. The advisory is shared at gist.github.com. This vulnerability is known as CVE-2022-1961 since 05/31/2022. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

By approaching the search of inurl:~/public/frontend.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Name

• Google Tag Manager Plugin

Version

• 1.15.0
• 1.15.1

License

• free

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion