CVE-2026-3138
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 · uneditedThe Product Filter for WooCommerce by WBW plugin for WordPress is vulnerable to unauthorized data loss due to a missing capability check in all versions up to, and including, 3.1.2. This is due to the plugin's MVC framework dynamically registering unauthenticated AJAX handlers via `wp_ajax_nopriv_` hooks without verifying user capabilities, combined with the base controller's `__call()` magic method forwarding undefined method calls to the model layer, and the `havePermissions()` method defaulting to `true` when no permissions are explicitly defined. This makes it possible for unauthenticated attackers to truncate the plugin's `wp_wpf_filters` database table via a crafted AJAX request with `action=delete`, permanently destroying all filter configurations.
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 confidenceThe plugin registers unauthenticated AJAX handlers via wp_ajax_nopriv_ hooks without capability verification, combined with a __call() magic method that forwards undefined method calls to the model layer and havePermissions() defaulting to true, allowing unauthenticated attackers to truncate the wp_wpf_filters database table via a crafted AJAX request with action=delete.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the plugin files in the WordPress installationInspect the wp-content/plugins directory for a folder that corresponds to the plugin containing a 'wp_wpf_filters' database table (commonly named something like 'wp-filters', 'wpf', or similar). Check the main plugin PHP file for the plugin name and version header.Affected if The plugin folder exists and contains the vulnerable plugin code.
-
Identify the installed plugin versionOpen the main plugin PHP file (usually named similarly to the plugin folder) and locate the Version header in the plugin comment block at the top. Compare this version number to the fixed version 3.1.3.Affected if The installed version is lower than 3.1.3.
-
Verify unauthenticated AJAX handlers existSearch the plugin source code for 'add_action' calls registering hooks with 'wp_ajax_nopriv_' prefix (e.g., 'wp_ajax_nopriv_delete' or similar). These enable unauthenticated access.Affected if The plugin registers any wp_ajax_nopriv_ hooks without additional capability checks.
-
Check the havePermissions() method implementationSearch the plugin code for a function or method named 'havePermissions()' or 'hasPermissions()'. Examine whether it returns true by default or lacks proper user capability verification.Affected if The havePermissions() method defaults to true or lacks role/capability verification.
-
Confirm the __call() magic method forwards to model layerSearch for a '__call' magic method in the plugin classes. Verify if it blindly forwards undefined method calls (like 'delete') to a model layer without permission checks.Affected if A __call() method exists that routes method calls to the model without authorization checks.
A user is affected if the plugin is installed with a version lower than 3.1.3 AND the plugin exposes unauthenticated AJAX endpoints with default-permissive havePermissions() logic that allows the delete action to execute without verification.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to version 3.1.3 or later which adds proper capability checks; alternatively, disable the plugin until a patch is available.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-3138 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3138 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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