Broken Link CheckerWordPress extension · Managewp
CVE-2023-23737
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 · uneditedUnauth. SQL Injection (SQLi) vulnerability in MainWP MainWP Broken Links Checker Extension plugin <= 4.0 versions.
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 confidenceUnauthenticated SQL injection vulnerability in the MainWP Broken Links Checker Extension plugin for WordPress affecting versions 4.0 and below. Attackers can inject malicious SQL queries via unsanitized input without requiring authentication, potentially allowing complete database compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Broken Link CheckerWordPress extension
<= 4.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the MainWP Broken Links Checker plugin is installedCheck your WordPress site's installed plugins list for 'MainWP Broken Links Checker Extension' or 'Managewp Broken Link Checker'. This can be done via WordPress admin dashboard under Plugins, or by checking the wp-content/plugins directory for a broken-links-checker folder.Affected if The plugin is present in the WordPress installation
-
Check the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and look for the version number listed under the plugin name. Alternatively, check the main plugin file (usually broken-link-checker.php or similar) in the plugin directory for the Version header in the plugin comment block.Affected if The version is 4.0 or below, or if the version cannot be determined but the plugin is present
-
Verify the plugin is activeIn WordPress admin under Plugins > Installed Plugins, confirm the plugin status shows as 'Active'. The vulnerability is exploitable without authentication when the plugin is installed AND active.Affected if The plugin is both installed and activated on the site
-
Check for suspicious database behavior or unauthorized accessReview WordPress database logs or server access logs for unusual SQL queries, especially those containing UNION SELECT, OR 1=1, or other SQL injection patterns targeting URLs or link-related parameters. Also check for unexpected database user accounts or modified wp_options entries.Affected if Suspicious SQL injection patterns are found in logs, or evidence of unauthorized database access is detected
You are affected if the MainWP Broken Links Checker Extension plugin version 4.0 or below is installed and active on your WordPress site.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the MainWP Broken Links Checker Extension to version 4.1 or later. If an update is unavailable, remove the plugin until a patch is released.
Fix this in Broken Link Checker
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23737 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-23737 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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