WpdatatablesWordPress extension · Tms Outsource

CVE-2021-24198

HIGH · 8.1 CVSS v3.1 Published 2021-04-12
Fix available
A fix is available. Upgrade to 3.4.2 or later.
See remediation →
87/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 wpDataTables – Tables & Table Charts premium WordPress plugin before 3.4.2 has Improper Access Control. A low privilege authenticated user that visits the page where the table is published can tamper the parameters to delete the data of another user that are present in the same table through id_key and id_val parameters. By exploiting this issue an attacker is able to delete the data of all users in the same table.

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 an Improper Access Control vulnerability allowing low-privilege authenticated users to delete data belonging to other users. Attackers exploit this by tampering with id_key and id_val parameters on pages where tables are published, effectively performing an IDOR (Insecure Direct Object Reference) attack that bypasses authorization checks.

MitigationUpdate wpDataTables to version 3.4.2 or later which contains proper access control validation for delete operations. Until patched, restrict publishing tables to administrator-level users only.

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 wpDataTables plugin is installed
    Navigate to WordPress admin dashboard > Plugins and locate wpDataTables in the installed plugins list. Note the installed version displayed in the plugin details.
    Affected if wpDataTables is not found in the plugins list, the vulnerability does not apply.
  2. Compare installed version to affected range
    Review the version number displayed for wpDataTables. The affected versions are any release before 3.4.2.
    Affected if The installed version is less than 3.4.2, the vulnerability is present in the environment.
  3. Identify published wpDataTables
    Visit the frontend of the website and locate any pages or posts where wpDataTables are embedded and visible. These are tables published using the plugin shortcodes.
    Affected if No tables are published publicly, the attack surface is limited but the vulnerability still exists in the plugin code.
  4. Verify low-privilege user access to published tables
    Using a low-privilege account (such as Subscriber or Contributor role), navigate to pages containing published wpDataTables and attempt to interact with table data deletion features if present.
    Affected if Low-privilege authenticated users can access published tables and trigger delete operations, they can exploit the IDOR vulnerability.

If wpDataTables version is below 3.4.2 and tables are published where any authenticated user can access them, the environment is affected by this IDOR vulnerability.

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

Update wpDataTables to version 3.4.2 or later which contains proper access control validation for delete operations. Until patched, restrict publishing tables to administrator-level users only.

Fix this in Wpdatatables Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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