Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCompromise admin credentials
-
DeliveryAuthenticate to WordPress dashboard
-
ExploitAccess Broken Link Checker plugin interface
-
ExecutionInject SQL payload in vulnerable parameter
-
PersistExecute blind SQLi extraction queries
-
ImpactExfiltrate database contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to possess WordPress high-privilege account credentials (Administrator or potentially Editor role with plugin access permissions). The Broken Link Checker plugin must be installed, activated, and accessible to the authenticated user role. Specific vulnerable functionality exists within database query handlers that accept user input from plugin interface fields (likely search, filter, or configuration parameters based on typical plugin architecture). The PR:H CVSS metric confirms that standard low-privilege WordPress Subscriber or Contributor accounts cannot exploit this vulnerability - only accounts with administrative database query privileges through the plugin's intended functionality are at risk. |
| Impact | Real-world exploitation risk is moderate despite the 7.6 CVSS score. Critical mitigating factors include the PR:H (High Privilege Required) authentication requirement, meaning only WordPress administrators or editors can exploit this vulnerability - significantly reducing the attack surface compared to unauthenticated SQLi. The EPSS score of 0.02% (6th percentile) indicates security researchers assess exploitation probability as very low in the next 30 days. No CISA KEV listing confirms this is not actively exploited in the wild. No publicly available POC exists per available data. The SSVC decision framework would classify this as: Exploitation Status (none public), Automatable (no - requires high-privilege authentication), Technical Impact (total for confidentiality given database access). Primary concern is insider threat scenarios or compromised administrator accounts being leveraged for data exfiltration. The Scope Change elevates risk slightly as successful exploitation could pivot from plugin context to full WordPress database access. Organizations should prioritize patching based on whether they grant WordPress administrative access to untrusted or semi-trusted users, and whether the plugin is actively installed and enabled. |
| Exploit ScenarioDerived | An attacker who has compromised WordPress administrator credentials (either through phishing, credential stuffing, or insider access) authenticates to the WordPress admin panel and navigates to the Broken Link Checker plugin interface. The attacker crafts malicious input containing SQL injection payloads in plugin parameters that interact with database queries, such as link URL filters or search fields. Using blind SQL injection techniques like time-based delays (SLEEP() functions) or boolean-based inference, the attacker systematically extracts sensitive data from the WordPress database including user credentials, customer information, or site configuration details, one character at a time over multiple requests. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 15, 2026
Blind SQL injection in WPMU DEV Broken Link Checker WordPress plugin versions ≤2.4.7 allows authenticated high-privilege users to extract database contents and potentially cause limited availability impact. CVSS 7.6 with scope change indicates potential container escape from plugin context. EPSS score of 0.02% (6th percentile) suggests low immediate exploitation likelihood. No public exploit code or CISA KEV listing identified at time of analysis. Patchstack discovery indicates vulnerability likely responsibly disclosed through bug bounty channel.
RemediationAI
Immediately upgrade Broken Link Checker plugin to a version newer than 2.4.7 when released by WPMU DEV. Monitor the WordPress.org plugin repository and WPMU DEV's official channels for security updates addressing CVE-2026-39466. As interim mitigation, organizations can restrict WordPress administrator role assignment to only fully trusted personnel, implement principle of least privilege by using Editor or lower roles where possible, enable WordPress security audit logging to detect suspicious database queries, deploy web application firewall rules to inspect SQL injection patterns in plugin requests, or temporarily deactivate the Broken Link Checker plugin if not business-critical until patched version is available. Review the Patchstack advisory at https://patchstack.com/database/Wordpress/Plugin/broken-link-checker/vulnerability/wordpress-broken-link-checker-plugin-2-4-7-sql-injection-vulnerability for additional vendor-specific remediation guidance. Consult NVD listing at https://nvd.nist.gov/vuln/detail/CVE-2026-39466 for updates on patch availability.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability exists in the Broken Link Checker plugin (CPE: cpe:2.3:a:wpmu_dev_-_your_all-in-one_wordpress_platform:broken_link_checker) developed by WPMU DEV for WordPress. The issue is classified as CWE-89 (SQL Injection), specifically manifesting as blind SQL injection where attacker-controlled input is insufficiently sanitized before incorporation into SQL queries. Blind SQL injection differs from traditional SQLi in that query results are not directly returned to the attacker; instead, exploitation relies on inferential techniques such as boolean-based or time-based attacks to extract data one bit at a time. The WordPress plugin architecture uses MySQL/MariaDB databases for storing site data, and inadequate input validation in plugin database queries can expose the entire WordPress database to unauthorized access. The 'S:C' (Scope Changed) CVSS metric indicates the vulnerability's impact extends beyond the plugin's security context, potentially affecting the broader WordPress installation or database.
Know when Broken Link Checker gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
Primary rating from Vendor (Patchstack) · only source for this CVE.
CVSS VectorVendor: Patchstack
Lifecycle Timeline
2DescriptionCVE.org
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.
Executive ViewAI
The WPMU DEV Broken Link Checker plugin (versions ≤2.4.7) contains a blind SQL injection vulnerability affecting authenticated high-privilege WordPress users, enabling unauthorized database extraction and potential service disruption. Organizations running this plugin must immediately restrict administrator access and prepare for urgent patching once the vendor releases a fix, as the vulnerability affects core data integrity despite current low exploitation likelihood.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict plugin access to minimal set of trusted administrators with enforce multi-factor authentication on all administrative accounts; (2) Implement database activity monitoring to detect anomalous queries; (3) Apply WAF rules to block SQL injection syntax in admin requests; (4) Consider temporary plugin deactivation if not essential to operations; (5) Monitor Patchstack and vendor advisory channels for patch availability.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Broken Link Checker
View allThe broken-link-checker plugin through 1.11.8 for WordPress (aka Broken Link Checker) is susceptible to Reflected XSS du
Unauth. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low
A reflected XSS vulnerability was found in includes/admin/table-printer.php in the broken-link-checker (aka Broken Link
The Broken Link Checker WordPress plugin before 1.11.20 does not sanitise and escape some of its settings, which could a
The Broken Link Checker WordPress plugin before 2.4.2 does not validate a the link URLs before making a request to them,
The Broken Link Checker plugin for WordPress is vulnerable to deserialization of untrusted input via the '$log_file' val
Stored XSS in the Broken Link Checker WordPress plugin (versions ≤ 2.4.13) allows unauthenticated attackers to inject pe
Arbitrary shortcode execution in the WordPress Broken Link Checker plugin (all versions up to and including 2.4.14.1) al
Cross-site scripting (XSS) vulnerability exists in the Wordpress admin panel when the Broken Link Checker plugin before
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPMU DEV Broken Li
Server-Side Request Forgery in the Broken Link Checker WordPress plugin (WPMU Dev, versions ≤ 2.4.14) allows high-privil
EUVD-2026-20137
GHSA-vvmg-mccx-3wpj
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB