Skip to main content
VulnerabilityPublished Updated

CVE-2026-14315: Pixel Tag Manager for WooCommerce (WordPress plugin) · Improper Access Control

Affects Pixel Tag Manager for WooCommerce (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.2.1 when convenient.

Data as of 1 Nov 2026, 08:20 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Upgrade Pixel Tag Manager for WooCommerce (WordPress plugin) to 2.2.1.

Affected software

ProductAffectedFixed in
Pixel Tag Manager for WooCommerceAffected
  • <2.2.1
Fixed in
  • 2.2.1

AI-suggested

If you cannot patch yet, restrict access to AJAX endpoints where possible and monitor for suspicious conversion event submissions.

Description

The Pixel Tag Manager for WooCommerce WordPress plugin before 2.2.1 does not perform an authorization check on one of its AJAX actions, allowing unauthenticated users to submit forged e-commerce conversion events to the site's configured server-side advertising conversion APIs using the site's stored credentials.

References

Community reviews

Loading reviews…