CVE-2019-15841

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

2019-06-18 00:00
Anonymous

Strategic Overview

Status
Patched in 1.9.15
Affected Plugin
Meta for WooCommerce
Affected Version
<= 1.9.12
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2019-15841
View all Meta for WooCommerce vulnerabilities

At a glance

CVE-2019-15841 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Meta for WooCommerce WordPress plugin, affecting versions <= 1.9.12. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.9.15; sites on affected versions should update now. Disclosed June 2019.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Meta for WooCommerce <= 1.9.12 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Meta for WooCommerce the fix is 1.9.15: builds <= 1.9.12 are affected, anything from 1.9.15 onward is not.

Remediation

Update to version 1.9.15, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Meta for WooCommerce: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Meta for WooCommerce 1.9.15 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C