CVE-2022-1707

Medium
6.1
0.05.010.0
Year
2022
Published
Jun 13, 2022
Known Affected Devices
0
CVSS Score
6.1

What is CVE-2022-1707?

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.

CVSS Vector Breakdown

CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
AV
Attack Vector
Network

Exploitable remotely over the network without requiring access to the local system.

AC
Attack Complexity
Low

No special conditions required. Exploit can be performed reliably and repeatedly.

PR
Privileges Required
None

No authentication required. Any anonymous user can exploit this vulnerability.

UI
User Interaction
Required

Victim must take an action (e.g. click a link, open a file) for the exploit to succeed.

S
Scope
Changed

Exploiting the vulnerability can affect other components beyond the vulnerable one.

C
Confidentiality Impact
Low

Some sensitive information is disclosed, but attacker has limited access.

I
Integrity Impact
Low

Attacker can modify some data, but scope or consequence is limited.

A
Availability Impact
None

No availability impact. Service remains fully operational.

Known Affected Devices

FAQ

How severe is CVE-2022-1707?

CVE-2022-1707 has a CVSS score of 6.1/10, rated as Medium. Review the affected products list and apply vendor patches.

What does the CVSS score mean for CVE-2022-1707?

CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2022-1707 scores 6.1/10 (Medium). Scores 9.0–10.0 are Critical, 7.0–8.9 are High, 4.0–6.9 are Medium, and below 4.0 are Low.

Which devices are affected by CVE-2022-1707?

The list of devices confirmed to be affected by CVE-2022-1707 is shown in the "Affected Devices" section above. Check your firmware version against the vendor security advisory and apply the latest patch.

How do I fix or mitigate CVE-2022-1707?

Apply the latest firmware or software update from the vendor. Check the References section above for official advisories and patch notes. If no patch is available, consider disabling the affected feature or isolating the device from untrusted networks.