Skip to content
Laskyr

Plugins · facebook-for-woocommerce · data as of 2026-11-01

Is Meta for WooCommerce safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (3.7.8)

As of 2026-11-01. 5 issues are on record for older versions; version 3.7.6 or newer fixes all of them that state a fix.

Latest version
3.7.8
Last updated
2026-10-08
Active installs
400,000+
Known issues on record
5
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 7.4+

Reach more customers and drive sales on Facebook, Instagram and WhatsApp with the official Meta for WooCommerce plugin. — by Facebook

What to do

  1. Update to the latest version (3.7.8). Anything older than 3.7.6 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. 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 facebook-for-woocommerce --field=version shows what you run; wp plugin update facebook-for-woocommerce updates it.

Check your version

Known vulnerabilities

5 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.

high 7.1 CVE-2026-66707 · published 2026-08-06

Cross-site scripting (XSS) in Meta for WooCommerce (3.7.5 and older)

Affected
3.7.5 and older
Fixed in
3.7.6
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

Unauthenticated Cross Site Scripting (XSS) in Facebook for WooCommerce <= 3.7.5 versions.

NVD CVE-2026-66707Patchstack advisory

medium 4.7 CVE-2026-49059 · published 2026-05-27

Open redirect in Meta for WooCommerce (3.7.0 and older)

Affected
3.7.0 and older
Fixed in
3.7.1 *
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

URL Redirection to Untrusted Site ('Open Redirect') vulnerability in Facebook Facebook for WooCommerce allows Phishing. This issue affects Facebook for WooCommerce: from n/a through 3.7.0.

NVD CVE-2026-49059Patchstack advisory

medium 5.3 CVE-2025-64296 · published 2025-10-29

Missing authorization check in Meta for WooCommerce (3.5.7 and older)

Affected
3.5.7 and older
Fixed in
3.5.8
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Patchstack
Details from the advisory

Missing Authorization vulnerability in Facebook Facebook for WooCommerce facebook-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Facebook for WooCommerce: from n/a through <= 3.5.7.

NVD CVE-2025-64296Patchstack advisory

high 8.8 CVE-2019-15840 · published 2019-08-30

Cross-site request forgery (CSRF) in Meta for WooCommerce (older than 1.9.14)

Affected
older than 1.9.14
Fixed in
1.9.14
Access needed (per CVSS)
No login needed; someone on the site has to click a link or open a page
Range from
NVD analysis · score by NVD
Details from the advisory

The facebook-for-woocommerce plugin before 1.9.14 for WordPress has CSRF.

NVD CVE-2019-15840wordpress.org

high 8.8 CVE-2019-15841 · published 2019-08-30

Cross-site request forgery (CSRF) in Meta for WooCommerce (older than 1.9.15)

Affected
older than 1.9.15
Fixed in
1.9.15
Access needed (per CVSS)
No login needed; someone on the site has to click a link or open a page
Range from
NVD analysis · score by NVD
Details from the advisory

The facebook-for-woocommerce plugin before 1.9.15 for WordPress has CSRF via ajax_woo_infobanner_post_click, ajax_woo_infobanner_post_xout, or ajax_fb_toggle_visibility.

NVD CVE-2019-15841wordpress.org

Recent activity

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Meta for WooCommerce vulnerability status badge
<a href="https://laskyr.com/plugins/facebook-for-woocommerce"><img src="https://laskyr.com/plugins/facebook-for-woocommerce/badge.svg" alt="Meta for WooCommerce vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Site hacked? Get help now
Run free scan Fix it now ($499) Send a message

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit