CVE-2019-20891: WooCommerce Cross-Site Request Forgery (CSRF)

woocommerce/woocommerce Updated 02 Oct 2025

Summary

24/05/2022
Yes i
High
8.8

CVE-2019-20891: WooCommerce Cross-Site Request Forgery (CSRF). Affects woocommerce/woocommerce versions < 3.6.5. Fixed in 3.6.5. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

WooCommerce is an open-source e-commerce plugin for WordPress. It provides a platform for creating online stores and managing products, orders, and payments. The vulnerability in WooCommerce versions before 3.6.5 affects the CSV import functionality, specifically the class-wc-product-csv-importer-controller.php file. This vulnerability allows for cross-site request forgery (CSRF) attacks, which can lead to stored cross-site scripting (XSS) attacks.

Vulnerability Detail

The vulnerability in WooCommerce allows an attacker to perform CSRF attacks by tricking a user into performing unintended actions on the affected website. By exploiting this vulnerability, an attacker can inject malicious code into the website, leading to stored XSS attacks. This can result in the execution of arbitrary code or the theft of sensitive information. The vulnerability has a CVSS score of 8.8, indicating a high severity level.

How To Fix

Minimum fixed version

3.6.5

This is the first release that contains the fix.

composer require woocommerce/woocommerce:3.6.5

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. However, website administrators can enhance security measures by implementing strong access controls, using web application firewalls, and regularly monitoring and auditing their websites for any suspicious activities or unauthorized changes.

Conclusion

The vulnerability in WooCommerce versions before 3.6.5 exposes websites to CSRF attacks and potential stored XSS attacks. To mitigate this risk, it is crucial to update WooCommerce to the latest version and regularly update plugins and themes. Implementing additional security measures, such as strong access controls and web application firewalls, can further enhance website security. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for woocommerce/woocommerce →

Share this vulnerability

FAQ

WooCommerce is an open-source e-commerce plugin for WordPress, providing a platform for creating online stores.

Cross-Site Request Forgery (CSRF) is an attack that tricks a user into performing unintended actions on a website without their knowledge or consent.

Cross-Site Scripting (XSS) is a type of security vulnerability that allows attackers to inject malicious scripts into web pages viewed by users.

This vulnerability can lead to the execution of arbitrary code or the theft of sensitive information, posing a significant risk to the affected website and its users.

Updating WooCommerce to version 3.6.5 or later and regularly updating plugins and themes are essential steps to mitigate the risk. Additionally, implementing strong access controls and using web application firewalls can enhance security measures.

Related vulnerabilities

Recent vulnerabilities recorded for woocommerce/woocommerce.

How To Fix

Minimum fixed version

3.6.5

This is the first release that contains the fix.

composer require woocommerce/woocommerce:3.6.5

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback