dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-12383

MEDIUM · 6.1 CVSS v3.1 Published 2025-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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 Binary MLM Woocommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0. This is due to missing or incorrect nonce validation on the 'bmw_display_pv_set_page' function and insufficient input sanitization and output escaping of the 'product_points' parameter. This makes it possible for unauthenticated attackers to inject arbitrary web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Binary MLM Woocommerce WordPress plugin lacks proper nonce validation on the bmw_display_pv_set_page function, allowing attackers to forge administrative requests. Combined with insufficient input sanitization and output escaping on the product_points parameter, this enables unauthenticated attackers to inject arbitrary web scripts via social-engineered CSRF attacks.

MitigationUpdate the plugin to version 2.1 or later which implements proper nonce validation and input sanitization for the product_points parameter.

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

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Verify Binary MLM WooCommerce plugin is installed
    Navigate to WordPress admin > Plugins and confirm 'Binary MLM WooCommerce' (or BMW) plugin is present and active, or check for directory wp-content/plugins/binary-mlm-woocommerce/ via file system
    Affected if Plugin is installed and active with version below 2.1
  2. Identify installed plugin version
    Open the main plugin file (e.g., binary-mlm-woocommerce.php) and locate the Version header in the plugin comment block, or check the readme.txt file for the Stable tag
    Affected if Version is below 2.1 (or version cannot be determined and plugin is present)
  3. Confirm vulnerable function is accessible
    Check if the bmw_display_pv_set_page function exists in the plugin source code (typically in admin/class-bmw-admin.php or similar). This function handles the product_points parameter in admin settings.
    Affected if Function exists without nonce validation (code review reveals missing wp_verify_nonce or check_admin_referer calls in bmw_display_pv_set_page)
  4. Verify product_points parameter handling
    Search plugin source for 'product_points' usage and confirm lack of sanitization (sanitize_text_field, intval, etc.) and output escaping (esc_html, esc_attr) when processing or displaying this parameter
    Affected if product_points is processed without proper sanitization and displayed without escaping

User is affected if Binary MLM WooCommerce plugin is installed with version below 2.1 and the bmw_display_pv_set_page function handles product_points without nonce validation and sanitization.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 2.1 or later which implements proper nonce validation and input sanitization for the product_points parameter.

Recommended fix Moderate confidence

Latest version of Binary MLM Woocommerce plugin (version > 2.0)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Binary MLM Woocommerce plugin
  4. Check if an update is available and update to the latest version
  5. Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin functions correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12383 — 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-2024-12383 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