CVE-2022-1707

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. Limited direct impact.

Exploit odds

89.3% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2022-05-13 00:00 UTC ReservedThe CVE id was reserved by its CNA
2. 2022-06-13 13:15 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-06-17 04:22 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 89.3% in the next 30 days (EPSS).
• Severity: 6.1 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2022-06-13 13:15 UTC

Last modified

2026-06-17 04:22 UTC

Exploit probability

89.3% · EPSS, next 30 days

Weakness

CWE-79 · Cross-site scripting

Record status

Modified

Affected

• gtm4wp Google Tag Manager < 1.15.1

Attack profile CVSS 3.1 · 6.1

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2022-1707.md and follow it. Check whether this project is affected by CVE-2022-1707. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge