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.
Product
wordpress woocommerce-conversion-tracking vulnerabilities
5 published CVES affecting wordpress woocommerce-conversion-tracking, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 0
- High
- 1
- Medium
- 4
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress woocommerce-conversion-tracking CVEs
Newest publication first
-
MediumCVSS 4.3 EPSS 0.11%
-
MediumCVSS 6.3 EPSS 0.23%
Missing Authorization vulnerability in weDevs WooCommerce Conversion Tracking.This issue affects WooCommerce Conversion Tracking: from n/a through 2.0.11.
-
MediumCVSS 4.3 EPSS 0.32%
Missing Authorization vulnerability in weDevs WooCommerce Conversion Tracking.This issue affects WooCommerce Conversion Tracking: from n/a through 2.0.11.
-
MediumCVSS 4.3
The Appsero analytics tool used in several plugins is vulnerable to authorization bypass due to a missing capability check on the uninstall_reason_submission function used for feedback submission in versions up to, and including, 1.2.1. This makes it possible for authenticated at...
-
HighCVSS 8.8
The WooCommerce Conversion Tracking plugin for WordPress is vulnerable to Cross-Site Request Forgery and Cross-Site Scripting in versions up to, and including, 2.0.4 due to insufficient input sanitization and output escaping along with insufficient nonce validation on the wcct_sa...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.