CVE-2026-14315

Pixel Tag Manager for WooCommerce – Google Analytics 4, Google Ads, and More Pixels < 2.2.1 - Unauthenticated Conversion Forge

2026-07-20 00:00

Strategic Overview

Status: Patched in 2.2.1
Affected Plugin: Pixel Tag Manager for WooCommerce – Google Analytics 4, Google Ads, and More Pixels
Affected Version: < 2.2.1
CVSS: 5.3Medium
Weakness type: CWE-862 · Missing Authorization
CVE: CVE-2026-14315

View all Pixel Tag Manager for WooCommerce – Google Analytics 4, Google Ads, and More Pixels vulnerabilities

At a glance

CVE-2026-14315 is a medium-severity Missing Authorization vulnerability in the Pixel Tag Manager for WooCommerce WordPress plugin, affecting versions < 2.2.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.2.1; sites on affected versions should update now. Disclosed July 2026, reported by Pedro Pinho.

Vulnerability Overview

The Pixel Tag Manager for WooCommerce – Google Analytics 4, Google Ads, and More Pixels plugin for WordPress is vulnerable to conversion forging in all versions up to 2.2.1 (exclusive). This makes it possible for unauthenticated attackers to forge conversion events.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Pixel Tag Manager for WooCommerce < 2.2.1 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Pixel Tag Manager for WooCommerce the fix is 2.2.1: builds < 2.2.1 are affected, anything from 2.2.1 onward is not.

Remediation

Update to version 2.2.1, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Pixel Tag Manager for WooCommerce 2.2.1 closes this, and updating the plugin is the step that ends it.

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-14315 https://www.wordfence.com/threat-intel/vulnerabilities/id/226c312e-38f0-4dac-bf5a-bce6df24aacc https://nvd.nist.gov/vuln/detail/CVE-2026-14315

CVSS Vector

5.3

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/