CVE-2026-39466

Broken Link Checker <= 2.4.7 - Authenticated (Editor+) SQL Injection

2026-03-26 00:00
daroo

Strategic Overview

Status
Patched in 2.4.8
Affected Plugin
Broken Link Checker
Affected Version
<= 2.4.7
CVSS
4.9Medium
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2026-39466
View all Broken Link Checker vulnerabilities

At a glance

CVE-2026-39466 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Broken Link Checker WordPress plugin, affecting versions <= 2.4.7. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 2.4.8; sites on affected versions should update now. Disclosed March 2026, reported by daroo.

Vulnerability Overview

The Broken Link Checker plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 2.4.7 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with editor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in Broken Link Checker <= 2.4.7 takes an account at Editor level or above. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Broken Link Checker the fix is 2.4.8: builds <= 2.4.7 are affected, anything from 2.4.8 onward is not.

Remediation

Update to version 2.4.8, or a newer patched version

How does WordSec protect against this?

An attacker needs Editor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Broken Link Checker 2.4.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-39466https://www.wordfence.com/threat-intel/vulnerabilities/id/4399c3b5-9bd6-4334-82fd-6afa735f89e0https://nvd.nist.gov/vuln/detail/CVE-2026-39466

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C