dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-54825

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

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
Unauthenticated SQL Injection in wpDataTables <= 7.4 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 confidence

Critical unauthenticated SQL injection vulnerability in wpDataTables plugin for WordPress versions 7.4 and below. An attacker without authentication can inject malicious SQL queries through vulnerable parameters, potentially allowing complete database compromise, data exfiltration, or further system access.

MitigationImmediately update wpDataTables to the latest version beyond 7.4. If no patched version is available, disable the plugin until a fix is released. Additionally, review database logs for suspicious SQL activity and consider temporary web application firewall protection.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify wpDataTables plugin version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins > wpDataTables. Locate the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file (typically in /wp-content/plugins/wpdatatables/) for the 'Version' header in the plugin comments.
    Affected if The installed version is 7.4 or any version number lower than 7.4.
  2. Verify plugin is active
    In WordPress admin, confirm wpDataTables plugin status shows as 'Active'. SQL injection can only be exploited when the plugin is enabled.
    Affected if The plugin is active and the version is 7.4 or below.
  3. Inspect access logs for SQL injection patterns
    Review web server access logs (Apache error_log, Nginx access.log, or WordPress debug.log if enabled) for unusual SQL syntax in GET/POST requests to /wp-json/wpdatatables/ endpoints or any wpdatatables-related URLs. Look for keywords like UNION, SELECT, INSERT, DROP, or common SQL function names.
    Affected if Log entries show SQL syntax appended to wpDataTables parameter values from unauthenticated sources.
  4. Check for unauthorized database changes
    Query WordPress database tables (particularly options table) for unexpected changes, new admin users, or modified user roles. Use phpMyAdmin or mysql CLI: SELECT * FROM wp_options WHERE option_name NOT LIKE 'wp%'; and review user table for unfamiliar administrators.
    Affected if Unknown admin accounts exist, user capabilities have been altered, or unexpected records appear in wp_options.

Your environment is affected if the wpDataTables plugin is active and the installed version is 7.4 or lower, or if logs show unauthenticated SQL patterns targeting wpDataTables endpoints.

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

Immediately update wpDataTables to the latest version beyond 7.4. If no patched version is available, disable the plugin until a fix is released. Additionally, review database logs for suspicious SQL activity and consider temporary web application firewall protection.

Recommended fix Moderate confidence

wpDataTables version greater than 7.4 (latest stable release)

  1. 1. Back up your WordPress database and files before making any changes.
  2. 2. Update wpDataTables plugin to the latest available version from the WordPress plugin repository or the vendor's official source.
  3. 3. Verify the update was successful by checking the plugin version in WordPress admin under Plugins.
  4. 4. Test critical table functionalities to ensure the update did not break existing data visualizations.
  5. 5. Consider running a security scan to confirm the vulnerability has been addressed.
Caveat Review plugin changelog for potential breaking changes between 7.4 and the target upgrade version before updating in production environments

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-2026-54825 — 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-54825 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