Plugins · woocommerce-conversion-tracking · data as of 2026-11-04
Is Conversion Tracking for WooCommerce safe? Known vulnerabilities and latest version
- Latest version
- 2.1.6
- Last updated
- 2026-10-06
- Active installs
- 20,000+
- Known issues on record
- 3
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
Adds various conversion tracking codes to cart, checkout, registration success and product page on WooCommerce — by weDevs
What to do
- Update to the latest version (2.1.6). Anything older than 2.0.12 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get woocommerce-conversion-tracking --field=version shows what you run; wp plugin update woocommerce-conversion-tracking updates it.
Check your version
Known vulnerabilities
3 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 4.3 CVE-2022-47150 · published 2026-06-11
Cross-site request forgery (CSRF) in Conversion Tracking for WooCommerce (2.0.10 and older)
- Affected
- 2.0.10 and older
- Fixed in
- 2.0.11
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Cross-Site request forgery (CSRF) vulnerability in weDevs WooCommerce Conversion Tracking allows Cross Site Request Forgery. This issue affects WooCommerce Conversion Tracking: from n/a through 2.0.10.
medium 6.3 CVE-2023-52217 · published 2024-06-11
Missing authorization check in Conversion Tracking for WooCommerce (2.0.11 and older)
- Affected
- 2.0.11 and older
- Fixed in
- 2.0.12
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Missing Authorization vulnerability in weDevs WooCommerce Conversion Tracking.This issue affects WooCommerce Conversion Tracking: from n/a through 2.0.11.
medium 4.3 CVE-2024-24711 · published 2024-03-26
Missing authorization check in Conversion Tracking for WooCommerce (2.0.11 and older)
- Affected
- 2.0.11 and older
- Fixed in
- 2.0.12
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in weDevs WooCommerce Conversion Tracking.This issue affects WooCommerce Conversion Tracking: from n/a through 2.0.11.
Recent activity
- 2026-10-06 — latest release on wordpress.org (2.1.6).
- 2026-06-11 — Cross-site request forgery (CSRF) disclosed (CVE-2022-47150), fixed in 2.0.11.
- 2024-06-11 — Missing authorization check disclosed (CVE-2023-52217), fixed in 2.0.12.
- 2024-03-26 — Missing authorization check disclosed (CVE-2024-24711), fixed in 2.0.12.
Get an email when Conversion Tracking for WooCommerce has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Conversion Tracking for WooCommerce (woocommerce-conversion-tracking) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by weDevs (7 tracked)
Types found in this plugin: Missing authorization (2) · Cross-site request forgery (CSRF) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/woocommerce-conversion-tracking (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/woocommerce-conversion-tracking"><img src="https://laskyr.com/plugins/woocommerce-conversion-tracking/badge.svg" alt="Conversion Tracking for WooCommerce vulnerability status"></a>