dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-64296

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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

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 · moderate confidence

Missing Authorization vulnerability in Facebook for WooCommerce plugin (versions <= 3.5.7) allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly validate authorization on certain functions or endpoints, potentially permitting unauthorized access to sensitive operations.

MitigationUpdate Facebook for WooCommerce to the latest version which includes proper authorization checks. If no update is available, review the plugin code to identify and add appropriate capability checks and authentication validation to all sensitive functions and AJAX endpoints.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Facebook for WooCommerce plugin is installed
    Navigate to WordPress admin > Plugins and confirm Facebook for WooCommerce appears in the installed plugins list, or query the database wp_plugins table for 'facebook-for-woocommerce'
    Affected if The plugin is installed and active
  2. Determine installed plugin version
    Check the plugin version in the plugin header (typically in the main plugin file like facebook-for-woocommerce.php) or via WordPress admin Plugins page > plugin details
    Affected if Version is 3.5.7 or lower
  3. Identify exposed AJAX endpoints
    Review plugin directory for PHP files registering AJAX actions (search for add_action("wp_ajax_) and check if these endpoints lack capability checks or nonce validation
    Affected if Plugin exposes AJAX endpoints without proper authorization checks
  4. Check for unprotected sensitive functions
    Examine plugin source code for functions handling sensitive operations (such as settings updates, order syncing, or data exports) that are missing current_user_can() checks or authentication validation
    Affected if Sensitive functions lack authorization validation before execution
  5. Test endpoint accessibility
    Use a tool like curl or Burp to send requests to common plugin AJAX endpoints (such as /wp-admin/admin-ajax.php?action=facebook_for_woocommerce*) without authentication credentials
    Affected if Requests are processed without requiring authentication or authorization

You are affected if Facebook for WooCommerce plugin version 3.5.7 or lower is installed and active, and the plugin exposes sensitive functions or AJAX endpoints that lack authorization 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.

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

Update Facebook for WooCommerce to the latest version which includes proper authorization checks. If no update is available, review the plugin code to identify and add appropriate capability checks and authentication validation to all sensitive functions and AJAX endpoints.

Recommended fix Moderate confidence

Version 3.5.8 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Facebook for WooCommerce' plugin
  4. 4. Check if an update is available for the plugin
  5. 5. If an update is available, update the plugin to the latest version (version 3.5.8 or later)
  6. 6. Verify the update was successful by checking the plugin version

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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