WpdatatablesWordPress extension · Tms Outsource

CVE-2021-24199

MEDIUM · 6.5 CVSS v3.1 Published 2021-04-12
Fix available
A fix is available. Upgrade to 3.4.2 or later.
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 wpDataTables – Tables & Table Charts premium WordPress plugin before 3.4.2 allows a low privilege authenticated user to perform Boolean-based blind SQL Injection in the table list page on the endpoint /wp-admin/admin-ajax.php?action=get_wdtable&table_id=1, on the 'start' HTTP POST parameter. This allows an attacker to access all the data in the database and obtain access to the WordPress application.

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 wpDataTables premium WordPress plugin before version 3.4.2 contains a Boolean-based blind SQL Injection vulnerability in the admin-ajax.php endpoint. The vulnerability exists in the 'start' POST parameter when accessing /wp-admin/admin-ajax.php?action=get_wdtable&table_id=1, allowing authenticated users with low privileges to inject arbitrary SQL queries and exfiltrate database contents.

MitigationUpgrade wpDataTables plugin to version 3.4.2 or later which contains the patched code. If immediate upgrade is not possible, restrict admin-ajax.php access or implement WAF rules to block SQL injection attempts on the affected endpoint.

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
WpdatatablesWordPress extension
Affected:< 3.4.2

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 wpDataTables plugin installation
    Check the WordPress plugins directory or inspect the plugin files. Look for wpdatatables folder in /wp-content/plugins/ and locate the main plugin file to read the version metadata.
    Affected if wpDataTables plugin is installed on the WordPress site
  2. Determine installed wpDataTables version
    Open the main plugin file (typically wpdatatables.php or similar) and locate the version comment header, or check the plugin metadata via WordPress admin plugins page.
    Affected if The installed version is less than 3.4.2 (e.g., 3.4.1, 3.4.0, earlier versions)
  3. Verify admin-ajax.php endpoint accessibility
    Check if the /wp-admin/admin-ajax.php endpoint is accessible on the WordPress site. This is typically accessible without authentication for logged-in users.
    Affected if The admin-ajax.php endpoint is reachable and responds to requests
  4. Confirm user role exposure
    Determine if low-privilege user accounts (subscriber, contributor, or custom low-privilege roles) can access the affected endpoint via the 'action=get_wdtable' parameter.
    Affected if Authenticated users with low privileges can access the vulnerable endpoint with the 'start' POST parameter

A site is affected if wpDataTables plugin version is below 3.4.2 AND the site has authenticated users who can access the admin-ajax.php endpoint with the get_wdtable action.

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
Upgrade available Upgrade to 3.4.2 or later
Fixed in 3.4.2
Interim mitigation

Upgrade wpDataTables plugin to version 3.4.2 or later which contains the patched code. If immediate upgrade is not possible, restrict admin-ajax.php access or implement WAF rules to block SQL injection attempts on the affected endpoint.

Fix this in Wpdatatables Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-24199 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-24199 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