dbcve.org
Facebook For WoocommerceWordPress extension · Facebook

CVE-2019-15841

HIGH · 8.8 CVSS v3.0 Published 2019-08-30
Fix available
A fix is available. Upgrade to 1.9.15 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The facebook-for-woocommerce plugin before version 1.9.15 lacks anti-CSRF token validation on three AJAX endpoints (ajax_woo_infobanner_post_click, ajax_woo_infobanner_post_xout, ajax_fb_toggle_visibility). An attacker can craft malicious links or pages that, when clicked by an authenticated admin, will trigger these endpoints to perform unintended state-changing actions (click tracking, dismissal actions, visibility toggles) without the user's consent.

MitigationImplement WordPress nonces (wp_verify_nonce or check_ajax_referer) on all three affected AJAX endpoints to validate request origin. Verify the nonce is included in the JavaScript and validated server-side before processing any state-changing operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Facebook For WoocommerceWordPress extension
Affected:< 1.9.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Facebook for WooCommerce. The version number is displayed below the plugin name. Alternatively, check the plugin header in facebook-for-woocommerce.php or the version in readme.txt inside the plugin folder.
    Affected if The version displayed is lower than 1.9.15 (e.g., 1.9.14, 1.9.13, etc.)
  2. Verify WordPress admin access
    Confirm you have administrator-level access to the WordPress site where the plugin is installed.
    Affected if You are an authenticated administrator on the WordPress site (the CVE requires an admin to be tricked into clicking a malicious link)
  3. Locate the affected AJAX endpoint code
    In the plugin folder (wp-content/plugins/facebook-for-woocommerce), search the main PHP file or ajax-handler files for one of these function names: ajax_woo_infobanner_post_click, ajax_woo_infobanner_post_xout, or ajax_fb_toggle_visibility. Use grep or a text editor search.
    Affected if The code for any of these endpoints exists and does NOT contain wp_verify_nonce, check_ajax_referer, or nonce verification before processing the request
  4. Inspect JavaScript enqueue for nonce token
    Check the plugin JavaScript files that call these AJAX endpoints. Look for a nonce parameter being passed (commonly named _wpnonce, security, or nonce) in the AJAX request data.
    Affected if The JavaScript making the AJAX call does NOT include a nonce token in the request data

You are affected if the Facebook for WooCommerce plugin version is below 1.9.15 AND the three AJAX endpoints (ajax_woo_infobanner_post_click, ajax_woo_infobanner_post_xout, ajax_fb_toggle_visibility) lack server-side nonce validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 1.9.15 or later
Fixed in 1.9.15
Interim mitigation

Implement WordPress nonces (wp_verify_nonce or check_ajax_referer) on all three affected AJAX endpoints to validate request origin. Verify the nonce is included in the JavaScript and validated server-side before processing any state-changing operations.

Fix this in Facebook For Woocommerce Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-15841 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-15841 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data