dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-39466

HIGH · 7.6 CVSS v3.1 Published 2026-04-08
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 WPMU DEV - Your All-in-One WordPress Platform Broken Link Checker broken-link-checker allows Blind SQL Injection.This issue affects Broken Link Checker: from n/a through <= 2.4.7.

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 · high confidence

A Blind SQL Injection vulnerability exists in the WPMU DEV Broken Link Checker plugin for WordPress (versions up to and including 2.4.7). The vulnerability allows unauthenticated attackers to inject malicious SQL queries through insufficiently sanitized user input, potentially enabling data exfiltration from the WordPress database.

MitigationUpdate Broken Link Checker to the latest patched version. As an interim measure, consider deploying a WAF rule to block SQL injection patterns and disable the plugin if an update is not available.

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. Verify Broken Link Checker plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Broken Link Checker' in the list. Alternatively, check the /wp-content/plugins/broken-link-checker/ directory exists on the server.
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, click on the Broken Link Checker plugin to view its details, or read the 'broken-link-checker.php' file header for the 'Version' value. Compare this version number to '2.4.7'.
    Affected if The installed version is 2.4.7 or any lower version number
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify that Broken Link Checker shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if The plugin is currently active and processing links
  4. Verify the plugin handles external input
    The vulnerability involves user-supplied data in SQL queries. Check if the plugin configuration allows custom link URLs or bulk link operations that could be processed by the plugin's database queries.
    Affected if The plugin is configured to process links or URLs provided by users or external sources

A WordPress site is affected if the Broken Link Checker plugin version 2.4.7 or lower is installed, active, and processing user-supplied link data through the plugin's database functionality.

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 Broken Link Checker to the latest patched version. As an interim measure, consider deploying a WAF rule to block SQL injection patterns and disable the plugin if an update is not available.

Recommended fix Moderate confidence

Latest version of Broken Link Checker plugin (check WordPress repository or WPMU DEV for version newer than 2.4.7)

  1. 1. Check current version of Broken Link Checker plugin installed on your WordPress site
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. If the installed version is 2.4.7 or lower, update the plugin to the latest available version
  4. 4. Before updating, backup your WordPress database and files
  5. 5. After updating, verify the plugin is functioning correctly and test the broken link checking functionality
  6. 6. Review activity logs to confirm no SQL injection exploitation occurred prior to patching

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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