dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-31425

HIGH · 7.5 CVSS v3.1 Published 2025-08-14
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 kamleshyadav WP Lead Capturing Pages leadcapture allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Lead Capturing Pages: from n/a through < 2.6.

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 WP Lead Capturing Pages plugin (leadcapture) versions prior to 2.6 contains a missing authorization vulnerability that allows unauthenticated attackers to exploit incorrectly configured access control security levels, potentially accessing or manipulating lead capture data without proper authentication.

MitigationUpdate WP Lead Capturing Pages plugin to version 2.6 or later to remediate the authorization flaw.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify WP Lead Capturing Pages plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WP Lead Capturing Pages' or 'leadcapture' in the plugin list
    Affected if Plugin is not found in the WordPress installation
  2. Check installed plugin version
    In the plugins list, click on the plugin to view details, or inspect the plugin header comment in /wp-content/plugins/leadcapture/leadcapture.php to find the Version: line
    Affected if Version field shows a version number lower than 2.6 (e.g., 2.5.x, 2.4.x, etc.)
  3. Identify plugin access control configuration
    Look for plugin settings pages under Leads or Lead Capturing Pages menu in WordPress admin. Check for any 'Security Level', 'Access Control', or 'Permission' settings that may be set to an insecure value (such as 'Anyone', 'Public', or disabled)
    Affected if Access control or security level is configured to allow unauthenticated or public access to lead data or submission features
  4. Test for unauthenticated lead data access
    Attempt to access lead capture data endpoints directly via HTTP request without logging in. Common paths may include /wp-json/leadcapture/leads or similar API endpoints. Use a tool like curl to request these URLs without authentication credentials
    Affected if HTTP response returns lead data, submission forms, or administrative functionality without requiring login credentials

The environment is affected if the WP Lead Capturing Pages plugin is installed with a version prior to 2.6 AND the access control security level is misconfigured to allow unauthenticated access.

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 WP Lead Capturing Pages plugin to version 2.6 or later to remediate the authorization flaw.

Recommended fix Moderate confidence

2.6

  1. Backup your WordPress site and database before making any changes
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Locate 'WP Lead Capturing Pages' by kamleshyadav
  4. Check the current version of the plugin - if it is below version 2.6, it is vulnerable
  5. Update the plugin to version 2.6 or later through the WordPress plugin updater, or download from wordpress.org
  6. Verify the update was successful by confirming the new version number
  7. Test the plugin functionality to ensure the update did not break existing features

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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