CVE-2020-36736
Summary
| CVE | CVE-2020-36736 |
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2023-07-01 04:15:00 UTC |
| Updated | 2023-11-07 03:22:00 UTC |
| Description | The WooCommerce Checkout & Funnel Builder by CartFlows plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.5.15. This is due to missing or incorrect nonce validation on the export_json, import_json, and status_logs_file functions. This makes it possible for unauthenticated attackers to import/export settings and trigger logs showing via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. |
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|
| 25 WordPress plugins vulnerable to CSRF attacks. – NinTechNet |
MISC |
blog.nintechnet.com |
|
| More WordPress plugins and themes vulnerable to CSRF attacks. – NinTechNet |
MISC |
blog.nintechnet.com |
|
| Multiple WordPress plugins fixed CSRF vulnerabilities (part 3). – NinTechNet |
MISC |
blog.nintechnet.com |
|
| Multiple WordPress plugins fixed CSRF vulnerabilities (part 2). – NinTechNet |
MISC |
blog.nintechnet.com |
|
| WooCommerce Checkout & Funnel Builder by CartFlows – Create High Converting Stores For WooCommerce <= 1.5.15 - Cross-Site Request Forgery Bypass |
MISC |
www.wordfence.com |
|
| Multiple WordPress plugins fixed CSRF vulnerabilities (part 4). – NinTechNet |
MISC |
blog.nintechnet.com |
|
| Multiple WordPress plugins fixed CSRF vulnerabilities (part 5). – NinTechNet |
MISC |
blog.nintechnet.com |
|
| 403 Forbidden |
MISC |
plugins.trac.wordpress.org |
|
| Multiple WordPress plugins fixed CSRF vulnerabilities (part 1). – NinTechNet |
MISC |
blog.nintechnet.com |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.