CVE-2026-16597 HIGH

CVE-2026-16597: GTM4WP <= 1.22.3 - Unauthenticated Stored Cross-Site Scripting via WooCommerce Billing Fields

Vendor Duracelltomi
Product GTM4WP – A Google Tag Manager (GTM) plugin for WordPress
Weakness CWE-79 · XSS
Published July 29, 2026
Last update July 29, 2026

CVSS base score

7.2/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

The GTM4WP – A Google Tag Manager (GTM) plugin for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via WooCommerce Billing Fields in all versions up to, and including, 1.22.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the GTM4WP WooCommerce order data integration option (GTM4WP_OPTION_INTEGRATE_WCORDERDATA) to be enabled, and is exploited by placing a guest checkout order with a JavaScript payload in a WooCommerce billing field such as the billing first name.

Explanation of Vulnerability in Simple Terms

02Summary

GTM4WP versions up to 1.22.3 contain a cross-site scripting (XSS) vulnerability that allows unauthenticated attackers to inject malicious scripts into the site. The vulnerability affects all visitors and can impact site integrity across multiple pages. Site owners should update to a version newer than 1.22.3 immediately.

What an attacker can do

03Attacker Capabilities

Inject malicious JavaScript that runs in visitors' browsers and affects site functionality.

Potential impact on your site

04Site Impact

Visitors' browsers execute attacker-controlled scripts, risking credential theft, malware, or site defacement.

Conditions required to exploit

05Prerequisites

No authentication or user interaction required; attacker can exploit this remotely.

Key dates

06Disclosure timeline

July 29, 2026 CVE published
July 29, 2026 Record updated

Related vulnerabilities

08Related CVE