dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-31580

HIGH · 7.5 CVSS v3.1 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Anzar Ahmed Ni WooCommerce Product Enquiry ni-woocommerce-product-enquiry allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Ni WooCommerce Product Enquiry: from n/a through <= 4.1.8.

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

The Ni WooCommerce Product Enquiry plugin before version 4.1.8 contains a missing authorization vulnerability where certain functionality is not properly constrained by access control lists. This allows users to access features they should not have permission to use, likely due to missing capability checks or nonce validation on AJAX endpoints.

MitigationUpdate to the latest version of the plugin when available. Until then, restrict the plugin to trusted users only and review the code for missing current_user_can() checks and nonce validations on sensitive AJAX actions.

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 the NI WooCommerce Product Enquiry plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'NI WooCommerce Product Enquiry' in the list. Note whether it is active or inactive.
    Affected if The plugin is active and the version is below 4.1.8
  2. Determine the installed plugin version
    Click on the plugin name in the Plugins page to view its details, or check the plugin header in the main PHP file (commonly in /wp-content/plugins/ni-woocommerce-product-enquiry/ or similar naming) for the Version field.
    Affected if The displayed version number is less than 4.1.8 (for example, 4.1.7, 4.1.0, or any version prior to 4.1.8)
  3. Identify plugin AJAX endpoints
    Search the plugin directory for 'add_action' calls registering AJAX handlers (typically 'wp_ajax_nopriv_' or 'wp_ajax_' hooks). Common locations include the main plugin file or includes/ajax.php. List each registered AJAX action name.
    Affected if AJAX endpoints exist and are accessible without authentication (wp_ajax_nopriv_) or without verified capability checks inside the handler
  4. Inspect AJAX handlers for capability checks
    Open the PHP file containing each AJAX handler callback. Look for 'current_user_can()' or similar authorization calls at the start of the function. Also check for 'wp_verify_nonce()' or 'check_ajax_referer()' validation calls.
    Affected if The AJAX handler function lacks a 'current_user_can()' check before executing sensitive functionality, or lacks nonce validation
  5. Test unauthorized access to AJAX functionality
    Using a tool like curl or Burp, send a request to the site's /wp-admin/admin-ajax.php endpoint with the action parameter matching one of the plugin's AJAX actions, without authenticating or providing valid credentials. Observe if the request is processed rather than rejected.
    Affected if The AJAX action responds with success or non-error data when accessed without proper authentication or authorization

A user is affected if the NI WooCommerce Product Enquiry plugin is installed, active, and running a version prior to 4.1.8, with AJAX endpoints that lack proper capability checks or 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the plugin when available. Until then, restrict the plugin to trusted users only and review the code for missing current_user_can() checks and nonce validations on sensitive AJAX actions.

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-2025-31580 — 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-31580 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