dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-31758

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 BinaryCarpenter Free Woocommerce Product Table View free-product-table-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Free Woocommerce Product Table View: from n/a through <= 1.78.

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 the Free Woocommerce Product Table View plugin allows authenticated users to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to restricted functionality or data due to improper capability or role verification.

MitigationUpdate the plugin to the latest version which should include proper authorization checks, or add WordPress capability checks and nonce verification to all admin/privileged functions within the plugin.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Confirm plugin installation
    Navigate to WordPress admin > Plugins and look for 'Free Woocommerce Product Table View' or check the /wp-content/plugins/ directory for a folder matching 'woo-product-table' or similar product table naming
    Affected if Plugin is present in the WordPress installation
  2. Identify installed version
    In WordPress admin, go to Plugins > Installed Plugins and locate the version number listed for 'Free Woocommerce Product Table View', or open the main plugin PHP file and read the 'Version' header in the plugin comment block
    Affected if Version cannot be determined or is older than the current stable release
  3. Verify admin function authorization
    Access the plugin directory and examine PHP files for functions handling admin or privileged actions. Search for patterns like 'add_action' or 'add_menu_page' and check if they include 'current_user_can()' capability checks before executing privileged operations
    Affected if Admin or privileged functions lack capability checks like current_user_can() or role verification
  4. Check AJAX action security
    Review the plugin's AJAX handlers (functions hooked to 'wp_ajax_' or 'wp_ajax_nopriv_' actions). Inspect whether these endpoints perform capability verification before returning sensitive data or executing restricted operations
    Affected if AJAX endpoints return restricted data or perform privileged actions without verifying user capabilities
  5. Test authenticated access boundaries
    Using an authenticated user account with subscriber or customer role (lowest privilege), attempt to access plugin admin URLs or functionality that should be restricted to administrators. Compare actual access against expected access control rules
    Affected if Lower-privileged authenticated users can access plugin functions or data intended only for administrators

If the plugin is installed and its admin/privileged functions lack capability verification (current_user_can checks), the environment is affected by this authorization bypass vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version which should include proper authorization checks, or add WordPress capability checks and nonce verification to all admin/privileged functions within the plugin.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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