dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-23784

HIGH · 7.6 CVSS v3.1 Published 2025-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 →
82/100
Remediation priority · High
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in David Jeffrey Contact Form 7 Round Robin Lead Distribution contact-form-7-round-robin-lead-distribution allows SQL Injection.This issue affects Contact Form 7 Round Robin Lead Distribution: from n/a through <= 1.2.1.

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

SQL Injection vulnerability in the Contact Form 7 Round Robin Lead Distribution WordPress plugin allows attackers to inject malicious SQL commands through unsanitized user inputs. This could enable unauthorized database access, data exfiltration, or modification of lead distribution records.

MitigationUpdate the plugin to the latest patched version once released. If no patch is available, disable the plugin and migrate to an alternative lead distribution solution. Review user input handling across the plugin and implement parameterized queries.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm plugin installation and activation status
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Contact Form 7 Round Robin Lead Distribution' in the list. Note whether it is installed and whether it shows as 'Active'.
    Affected if The plugin is installed and active - only active plugins can process requests and be exploited.
  2. Identify installed plugin version
    In the plugins list, click on the plugin name or view the plugin details to find the version number displayed under the plugin name. Alternatively, inspect the plugin main file header in wp-content/plugins/ for the 'Version' tag.
    Affected if The installed version is unpatched - without a specific version range, treat any version as potentially affected until the vendor releases a patch.
  3. Verify plugin handles user-submitted data
    Check if the plugin is connected to any Contact Form 7 forms. Go to the plugin settings page (usually under Contact > Round Robin or similar) and list any forms configured for lead distribution.
    Affected if The plugin is actively distributing leads from forms - this indicates user input flows through the plugin, which is required for SQL injection exploitation.
  4. Check for public-facing form submissions
    Review the WordPress site's front-end for any forms (contact forms, lead capture forms) that use the Round Robin distribution feature. Note the form IDs or keys used.
    Affected if Public forms accept user input that gets processed by the vulnerable code path - these inputs are the injection vectors.
  5. Inspect plugin database query handling
    Access the plugin files via FTP or file manager. Locate PHP files in the plugin directory (typically wp-content/plugins/contact-form-7-round-robin-lead-distribution/). Search for direct SQL queries using $wpdb->prepare, $wpdb->query, or raw SQL concatenation.
    Affected if Unsanitized user input is used in SQL queries - look for patterns where form submission data (like name, email, or custom fields) is concatenated directly into SQL statements without proper escaping or prepared statements.

Your environment is affected if the Contact Form 7 Round Robin Lead Distribution plugin is active, processes form submissions, and contains SQL queries that use user input without proper sanitization or prepared statements.

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 patched version once released. If no patch is available, disable the plugin and migrate to an alternative lead distribution solution. Review user input handling across the plugin and implement parameterized queries.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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