dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-67962

HIGH · 7.6 CVSS v3.1 Published 2025-12-16
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 AIOSEO Plugin Team Broken Link Checker broken-link-checker-seo allows SQL Injection.This issue affects Broken Link Checker: from n/a through <= 1.2.6.

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 confidence

SQL injection vulnerability in the Broken Link Checker WordPress plugin (broken-link-checker-seo) allows attackers to inject malicious SQL commands through unsanitized input in database queries, potentially enabling unauthorized data access or manipulation.

MitigationUpdate the Broken Link Checker plugin to a patched version once released; if no patch is available, disable the plugin until a fix can be applied.

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. Locate the Broken Link Checker plugin files
    Check your WordPress installation's wp-content/plugins/ directory for a folder named 'broken-link-checker' or 'broken-link-checker-seo'. If using a managed WordPress host, access via FTP, file manager, or WP-CLI: `wp plugin list --search='broken*link*'`
    Affected if The plugin folder exists in the plugins directory and the plugin is installed on the site
  2. Identify the installed plugin version
    Open the main plugin file (typically broken-link-checker.php) and locate the 'Version' header in the plugin comment block at the top. Alternatively, run: `grep -i 'Version:' wp-content/plugins/broken-link-checker/broken-link-checker.php`
    Affected if The version number displayed matches a version known to be affected by CVE-2025-67962 (compare against the affected version range for this CVE)
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify Broken Link Checker shows as 'Active'. Alternatively, query the database: `SELECT * FROM wp_options WHERE option_name = 'active_plugins';` and check if the plugin is in the active list
    Affected if The plugin is currently active on the WordPress site, enabling the vulnerable code paths
  4. Review access to the vulnerable query function
    The SQL injection exists in unsanitized database queries within the plugin. Check if the plugin's admin interface or any public-facing AJAX endpoints are accessible. Inspect network requests to /wp-admin/admin-ajax.php or the plugin's settings page for unusual query parameters
    Affected if Unsanitized user input can reach the plugin's database query functions, typically through the admin dashboard or AJAX actions

Your environment is affected if the Broken Link Checker (or broken-link-checker-seo) plugin is installed, active, and runs a version within the affected range for CVE-2025-67962.

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 the Broken Link Checker plugin to a patched version once released; if no patch is available, disable the plugin until a fix can be applied.

Recommended fix Moderate confidence

Latest version of Broken Link Checker (version > 1.2.6)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Broken Link Checker' plugin in the list
  4. If an update is available, click 'Update now' to install the latest version (version > 1.2.6)
  5. Alternatively, manually download the latest version from the WordPress plugin repository and reinstall

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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