dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-2279

HIGH · 7.2 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/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
The myLinksDump plugin for WordPress is vulnerable to SQL Injection via the 'sort_by' and 'sort_order' parameters in all versions up to, and including, 1.6 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 administrator-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 myLinksDump WordPress plugin is vulnerable to SQL injection in versions up to 1.6 via the 'sort_by' and 'sort_order' parameters. Insufficient input sanitization combined with lack of prepared statements in the SQL queries allows authenticated administrators to inject arbitrary SQL commands and extract sensitive database information.

MitigationImplement proper input validation and escaping for the 'sort_by' and 'sort_order' parameters, or refactor to use WordPress $wpdb prepare() method for parameterized queries. Update to version 1.7 or later once available.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm myLinksDump plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'myLinksDump' in the list. Note the version number displayed under the plugin name.
    Affected if Plugin is installed and version is 1.6 or lower
  2. Verify plugin version against affected range
    Compare the installed version to the affected range. The vulnerability affects versions up to and including 1.6. Check the plugin header in mylinksdump.php for the Version: field, or query the WordPress options table: SELECT option_value FROM wp_options WHERE option_name = 'myLinksDump_version' (table prefix may vary).
    Affected if Installed version is 1.6 or lower (versions 1.7+ contain the fix)
  3. Confirm administrator-level access exists
    The SQL injection requires an authenticated administrator account. Check WordPress user roles: go to Users > All Users and verify if any account has 'Administrator' role. The vulnerability cannot be exploited by lower-privileged users or unauthenticated attackers.
    Affected if At least one user with Administrator role exists and has an active session
  4. Inspect vulnerable parameter handling
    Examine the plugin file (typically wp-content/plugins/mylinksdump/mylinksdump.php or similar path). Search for 'sort_by' and 'sort_order' in the code. Look for direct use of these parameters in SQL queries without $wpdb->prepare() or sanitization functions like sanitize_sql_orderby() or esc_sql().
    Affected if Code uses $_GET or $_POST['sort_by']/'sort_order' directly in SQL without prepared statements or input validation

You are affected if the myLinksDump plugin is installed with version 1.6 or lower AND an administrator account can access the vulnerable parameter handling code.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and escaping for the 'sort_by' and 'sort_order' parameters, or refactor to use WordPress $wpdb prepare() method for parameterized queries. Update to version 1.7 or later once available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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