Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Plugin security history

Meta for WooCommerce Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 4 vulnerability records associated with Meta for WooCommerce, published between 2019 and 2026.

Dataset last synchronized: 2026-08-03 00:31:25 UTC

At a glance

Security Snapshot

4Total records
0Critical
2High
2Medium
0Low
0Informational
4Patched records
0Currently marked unpatched
2019-06-18First disclosure
2026-05-27Latest disclosure
4 of 4CVE coverage

Year-by-Year Timeline

YearRecordsRelative volume
201922 records
202511 records
202611 records

Severity Breakdown

SeverityRecordsShare
High250%
Medium250%

Vulnerability-Type Breakdown

CSRF

2 records50%

First: 2019. Latest: 2019.

Missing Authorization

1 record25%

First: 2025. Latest: 2025.

Other

1 record25%

First: 2026. Latest: 2026.

Patch Status

Patched
4
Currently marked unpatched
0
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

  • 3.7.1
  • 3.5.8
  • 1.9.15

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-3.7.0Meta for WooCommerce <= 3.7.0 - Unauthenticated Open RedirectMay 27, 20263.7.1Medium
*-3.5.7Facebook for WooCommerce <= 3.5.7 - Missing Authorization to Unauthenticated Notification DismissalOctober 29, 20253.5.8Medium
*-1.9.12Facebook for WooCommerce <= 1.9.12 - Cross-Site Request Forgery allowing Option UpdateJune 18, 20191.9.15High
*-1.9.12Facebook for WooCommerce <= 1.9.12 - Cross-Site Request ForgeryJune 18, 20191.9.15High

Selected source records

Latest Records

MediumCVE-2026-49059

Meta for WooCommerce <= 3.7.0 - Unauthenticated Open Redirect

Published: May 27, 2026

Affected versions
*-3.7.0
Patched versions
3.7.1
Original Wordfence record
MediumCVE-2025-64296

Facebook for WooCommerce <= 3.5.7 - Missing Authorization to Unauthenticated Notification Dismissal

Published: October 29, 2025

Affected versions
*-3.5.7
Patched versions
3.5.8
Original Wordfence record
HighCVE-2019-15840

Facebook for WooCommerce <= 1.9.12 - Cross-Site Request Forgery

Published: June 18, 2019

Affected versions
*-1.9.12
Patched versions
1.9.15
Original Wordfence record
HighCVE-2019-15841

Facebook for WooCommerce <= 1.9.12 - Cross-Site Request Forgery allowing Option Update

Published: June 18, 2019

Affected versions
*-1.9.12
Patched versions
1.9.15
Original Wordfence record

Highest-Severity Records

HighCVE-2019-15840

Facebook for WooCommerce <= 1.9.12 - Cross-Site Request Forgery

Published: June 18, 2019

Affected versions
*-1.9.12
Patched versions
1.9.15
Original Wordfence record
HighCVE-2019-15841

Facebook for WooCommerce <= 1.9.12 - Cross-Site Request Forgery allowing Option Update

Published: June 18, 2019

Affected versions
*-1.9.12
Patched versions
1.9.15
Original Wordfence record
MediumCVE-2025-64296

Facebook for WooCommerce <= 3.5.7 - Missing Authorization to Unauthenticated Notification Dismissal

Published: October 29, 2025

Affected versions
*-3.5.7
Patched versions
3.5.8
Original Wordfence record
MediumCVE-2026-49059

Meta for WooCommerce <= 3.7.0 - Unauthenticated Open Redirect

Published: May 27, 2026

Affected versions
*-3.7.0
Patched versions
3.7.1
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.

Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.

Data Source, Attribution and Methodology

This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.

Return to the Security History Directory