dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-1264

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
The Broken Link Checker by AIOSEO – Easily Fix/Monitor Internal and External links plugin for WordPress is vulnerable to SQL Injection via the 'orderBy' parameter in all versions up to, and including, 1.2.3 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 Contributor-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 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 · high confidence

The Broken Link Checker by AIOSEO WordPress plugin (versions up to 1.2.3) contains a SQL Injection vulnerability via the 'orderBy' parameter. Insufficient escaping of user input combined with lack of prepared statements in the SQL query allows authenticated users with Contributor-level access or higher to inject arbitrary SQL queries and extract sensitive data from the database.

MitigationUpdate the plugin to version 1.2.4 or later which contains the security fix. Alternatively, implement proper input validation and use prepared statements for all SQL queries.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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. Identify plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > look for 'Broken Link Checker by AIOSEO' and note the version number displayed
    Affected if The version shown is 1.2.3 or lower (any version up to and including 1.2.3)
  2. Confirm plugin is active
    Check the Plugins list in WordPress admin - verify the plugin is installed and currently activated
    Affected if The plugin is activated and the version is 1.2.3 or lower
  3. Check WordPress user roles
    Navigate to WordPress admin > Users and review the roles assigned to site users; specifically identify any users with Contributor, Author, Editor, or Administrator roles
    Affected if The plugin is vulnerable AND there exists at least one user with Contributor-level access or higher (this role can trigger the vulnerable code path)
  4. Verify plugin files exist
    If server access is available, check the plugin directory at /wp-content/plugins/broken-link-checker-aio-seo/ and locate the main plugin file to confirm version
    Affected if Plugin files exist and version in the plugin header is 1.2.3 or lower

The environment is affected if the Broken Link Checker by AIOSEO plugin is installed, activated, and running version 1.2.3 or lower.

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 plugin to version 1.2.4 or later which contains the security fix. Alternatively, implement proper input validation and use prepared statements for all SQL queries.

Recommended fix High confidence

1.2.4 or latest available version

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Broken Link Checker by AIOSEO'
  4. Check if an update is available and update to version 1.2.4 or higher
  5. Alternatively, download the latest version from wordpress.org/plugins/broken-link-checker/ and upload via Plugins > Add New > Upload Plugin

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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