Skip to main content

Broken Link Checker EUVDEUVD-2026-20137

| CVE-2026-39466 HIGH
SQL Injection (CWE-89)
2026-04-08 Patchstack GHSA-vvmg-mccx-3wpj
7.6
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Compromise admin credentials
  2. Delivery
    Authenticate to WordPress dashboard
  3. Exploit
    Access Broken Link Checker plugin interface
  4. Execution
    Inject SQL payload in vulnerable parameter
  5. Persist
    Execute blind SQLi extraction queries
  6. Impact
    Exfiltrate 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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Broken Link Checker 0 ≤2.4.7

Affected Packages

euvd broken_link_checker no fix

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

Vendor (Patchstack) PRIMARY 7.6 HIGH
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

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

Lifecycle Timeline

2
CVSS changed
Apr 13, 2026 - 17:22 NVD
7.6 (HIGH)
CVE Published
Apr 08, 2026 - 08:30 nvd
N/A

DescriptionCVE.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

Why It Matters

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.0%
Top 94% exploitable
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

CVE-2019-16521 MEDIUM POC
6.1 Oct 16

The broken-link-checker plugin through 1.11.8 for WordPress (aka Broken Link Checker) is susceptible to Reflected XSS du

CVE-2023-23737 CRITICAL
9.8 Oct 12

Unauth. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low

CVE-2019-17207 MEDIUM POC
5.4 Oct 18

A reflected XSS vulnerability was found in includes/admin/table-printer.php in the broken-link-checker (aka Broken Link

CVE-2022-3922 MEDIUM POC
4.8 Dec 28

The Broken Link Checker WordPress plugin before 1.11.20 does not sanitise and escape some of its settings, which could a

CVE-2024-10903 MEDIUM POC
4.7 Dec 26

The Broken Link Checker WordPress plugin before 2.4.2 does not validate a the link URLs before making a request to them,

CVE-2022-2438 HIGH
7.2 Sep 06

The Broken Link Checker plugin for WordPress is vulnerable to deserialization of untrusted input via the '$log_file' val

CVE-2026-75528 HIGH
7.2 Sep 02

Stored XSS in the Broken Link Checker WordPress plugin (versions ≤ 2.4.13) allows unauthenticated attackers to inject pe

CVE-2026-96562 MEDIUM
6.5 Oct 16

Arbitrary shortcode execution in the WordPress Broken Link Checker plugin (all versions up to and including 2.4.14.1) al

CVE-2015-5057 MEDIUM
6.1 Aug 18

Cross-site scripting (XSS) vulnerability exists in the Wordpress admin panel when the Broken Link Checker plugin before

CVE-2024-25592 MEDIUM
5.9 Mar 15

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPMU DEV Broken Li

CVE-2026-84772 MEDIUM
5.5 Sep 02

Server-Side Request Forgery in the Broken Link Checker WordPress plugin (WPMU Dev, versions ≤ 2.4.14) allows high-privil

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy