dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-49055

CRITICAL · 9.3 CVSS v3.1 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in kamleshyadav WP Lead Capturing Pages wp-lead-capture allows Blind SQL Injection.This issue affects WP Lead Capturing Pages: from n/a through <= 2.5.

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

A blind SQL injection vulnerability exists in the WP Lead Capturing Pages WordPress plugin (versions <= 2.5) by kamleshyadav. The vulnerability allows unauthenticated attackers to inject malicious SQL commands through improper neutralization of special elements in SQL queries. With a CVSS score of 9.3 (Critical), successful exploitation can lead to complete database compromise, including extraction of sensitive data or potential system access.

MitigationUpgrade WP Lead Capturing Pages to the latest version immediately. If no patched version is available, remove the plugin or implement WAF rules to block SQL injection attack patterns until a fix is released.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin installation
    Log into WordPress admin, navigate to Plugins > Installed Plugins, and search for 'WP Lead Capturing Pages' or check the plugin directory /wp-content/plugins/ for a folder named 'lead-capturing-pages' or similar.
    Affected if The plugin is not found in the WordPress installation
  2. Check installed version
    In WordPress admin > Plugins > Installed Plugins, find WP Lead Capturing Pages and view the version number displayed beneath the plugin name. Alternatively, inspect the main plugin PHP file header for the 'Version' field.
    Affected if The displayed version is 2.5 or lower, or if the version field cannot be read but the plugin is present
  3. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify that WP Lead Capturing Pages shows an 'Active' status under the plugin name.
    Affected if The plugin is active and processing requests
  4. Identify vulnerable code path
    Review any publicly available proof-of-concept or vulnerability disclosure to identify which plugin feature handles user input in SQL queries (typically lead form submissions). Test submitting a form with a simple time-based SQL payload (e.g., SLEEP(5)) if authorized.
    Affected if The plugin processes lead capture form submissions without proper SQL parameterization

If WP Lead Capturing Pages is installed, active, and running version 2.5 or lower, the environment is vulnerable to unauthenticated blind SQL injection via the plugin's form handling logic.

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

Upgrade WP Lead Capturing Pages to the latest version immediately. If no patched version is available, remove the plugin or implement WAF rules to block SQL injection attack patterns until a fix is released.

Recommended fix Moderate confidence

Latest available version of WP Lead Capturing Pages (wp-lead-capture) plugin (version greater than 2.5)

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate 'WP Lead Capturing Pages' (wp-lead-capture) in the plugin list.
  4. 4. Check the current version number displayed under the plugin name.
  5. 5. If your current version is 2.5 or below, click 'Update Now' if an update is available, or manually download the latest version from the WordPress Plugin Repository.
  6. 6. After updating, verify the plugin is functioning correctly by testing any lead capture forms on your site.
  7. 7. Monitor the site for any errors or unusual behavior following the update.
Caveat Review plugin settings and form functionality after upgrade as minor layout or option changes may occur in newer versions

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
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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