dbcve.org
WpdatatablesWordPress extension · Tms Outsource

CVE-2023-23876

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-03
Fix available
A fix is available. Upgrade to 2.1.50 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in TMS-Plugins wpDataTables plugin <= 2.1.49 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 · high confidence

A stored Cross-Site Scripting (XSS) vulnerability exists in the wpDataTables plugin for WordPress versions 2.1.49 and below. Authenticated users with contributor-level permissions or higher can inject malicious JavaScript payloads that persist in the database and execute when other users view the affected content.

MitigationUpdate the wpDataTables plugin to a version newer than 2.1.49. Review and sanitize any existing entries in the database that may contain malicious scripts.

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:< 2.1.50

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Check installed wpDataTables version
    In WordPress admin, go to Plugins > Installed Plugins > wpDataTables, or check the version in the plugin's main PHP file header
    Affected if The version listed is 2.1.49 or lower
  2. Verify contributor-level user access exists
    Check WordPress user roles at Users > All Users - look for any users with Contributor, Author, Editor, or Administrator roles who have access to wpDataTables
    Affected if Any user with Contributor-level or higher permissions can access the plugin's table editing features
  3. Inspect database for suspicious table content
    Query the wp_datatables tables (typically wp_wpdatatables or similar) for any entries containing script tags, javascript:, or onload/onerror attributes in data fields
    Affected if Malicious JavaScript payloads are present in table cell data
  4. Check for recently created or modified tables
    Review table creation/modification timestamps in the wp_wpdatatables table - compare against expected activity
    Affected if Tables were created or modified by lower-privilege users without corresponding admin records
  5. Examine table rendering in frontend
    View published wpDataTables on the frontend and inspect page source for any unsanitized user content that could execute
    Affected if User-supplied content renders as raw HTML/JavaScript rather than being escaped

A user is affected if wpDataTables version is 2.1.49 or below AND any contributor-level user has access to create or edit tables containing unsanitized content.

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

Update the wpDataTables plugin to a version newer than 2.1.49. Review and sanitize any existing entries in the database that may contain malicious scripts.

Recommended fix High confidence

wpDataTables version 2.1.50

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate wpDataTables in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 2.1.50 or later
  5. 5. Alternatively, navigate to Dashboard > Updates to check for and apply available updates
  6. 6. After updating, verify the plugin is running version 2.1.50 or higher by checking the Plugins page

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

Fix this in Wpdatatables Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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