Meta for WooCommerce at a glance
- 5 publicly disclosed vulnerabilities, 3 of them rated High or Critical. The most recent was disclosed on Jul 31, 2026.
- Ranked #138 by popularity on WordPress.org (400,000+ active installs).
- The latest version is 3.7.9 (released Nov 17, 2026). The most recent security fix shipped in 3.7.6.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Meta for WooCommerce version
Enter the Meta for WooCommerce version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Meta for WooCommerce”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Meta for WooCommerce”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (3.7.9). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Meta for WooCommerce vulnerabilities
Meta for WooCommerce <= 3.7.5 - Unauthenticated Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-66707
Affected versions: ≤ 3.7.5
Fixed in: 3.7.6
Severity: High 7.2 · Disclosed Jul 31, 2026
Meta for WooCommerce <= 3.7.0 - Unauthenticated Open Redirect
Open redirect · CVE-2026-49059
Affected versions: ≤ 3.7.0
Fixed in: 3.7.1
Severity: Medium 4.7 · Disclosed May 27, 2026
Facebook for WooCommerce <= 3.5.7 - Missing Authorization to Unauthenticated Notification Dismissal
Missing authorization · CVE-2025-64296
Affected versions: ≤ 3.5.7
Fixed in: 3.5.8
Severity: Medium 5.3 · Disclosed Oct 29, 2025
Facebook for WooCommerce <= 1.9.12 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2019-15840
Affected versions: ≤ 1.9.12
Fixed in: 1.9.15
Severity: High 8.8 · Disclosed Jun 18, 2019
Facebook for WooCommerce <= 1.9.12 - Cross-Site Request Forgery allowing Option Update
Cross-site request forgery (CSRF) · CVE-2019-15841
Affected versions: ≤ 1.9.12
Fixed in: 1.9.15
Severity: High 8.8 · Disclosed Jun 18, 2019
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Meta for WooCommerce <= 3.7.5 - Unauthenticated Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-66707 | ≤ 3.7.5 | 3.7.6 | High 7.2 | Jul 31, 2026 |
| Meta for WooCommerce <= 3.7.0 - Unauthenticated Open RedirectOpen redirect · CVE-2026-49059 | ≤ 3.7.0 | 3.7.1 | Medium 4.7 | May 27, 2026 |
| Facebook for WooCommerce <= 3.5.7 - Missing Authorization to Unauthenticated Notification DismissalMissing authorization · CVE-2025-64296 | ≤ 3.5.7 | 3.5.8 | Medium 5.3 | Oct 29, 2025 |
| Facebook for WooCommerce <= 1.9.12 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2019-15840 | ≤ 1.9.12 | 1.9.15 | High 8.8 | Jun 18, 2019 |
| Facebook for WooCommerce <= 1.9.12 - Cross-Site Request Forgery allowing Option UpdateCross-site request forgery (CSRF) · CVE-2019-15841 | ≤ 1.9.12 | 1.9.15 | High 8.8 | Jun 18, 2019 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Jul 31, 2026.
Most common weaknesses in Meta for WooCommerce
Cross-site request forgery (CSRF)
2 issues
If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.
Cross-site scripting (XSS)
1 issue
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Open redirect
1 issue
Links on your own domain can be used to send people to a fake site, which makes phishing emails look more convincing.
Frequently asked questions
Is Meta for WooCommerce safe to use?
Meta for WooCommerce is a well-known plugin with 400,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.7.9) and turn on automatic updates.
How do I find which version of Meta for WooCommerce my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesMeta for WooCommerce on WordPress.org