Pixel Tag Manager lets visitors forge server-side advertising conversions
Pixel Tag Manager for WooCommerce before 2.2.1 exposes an AJAX action without an authorization check. An unauthenticated visitor can submit attacker-controlled e-commerce conversion data, which the plugin forwards to configured server-side advertising conversion APIs using credentials stored by the site owner. The record does not disclose the AJAX action, event parameters, callback or external API methods.
- Component
- Pixel Tag Manager for WooCommerce
- Plugin slug
pixel-tag-manager-for-woocommerce- Affected
- < 2.2.1
- Safe version
2.2.1- Published
- Aug 01, 2026
- Weakness
- Not assigned
This CVE was published Aug 01, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update Pixel Tag Manager for WooCommerce to 2.2.1 or later. Reconcile server-side conversion events with real WooCommerce orders, review unauthenticated AJAX traffic for fabricated event data, remove false conversions where supported, and rotate advertising API credentials if broader misuse is suspected.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical 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.