Skip to main content

wpDataTables CVE-2026-49080

| EUVDEUVD-2026-37496 CRITICAL
SQL Injection (CWE-89)
2026-06-16 Patchstack
9.3
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Fingerprint WordPress site running wpDataTables
  2. Delivery
    Identify vulnerable AJAX/REST endpoint
  3. Exploit
    Inject SQL via table/filter parameter
  4. Execution
    Enumerate schema via UNION or blind techniques
  5. Persist
    Exfiltrate wp_users hashes and secrets
  6. Impact
    Crack hashes and authenticate as admin

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No special conditions - remote unauthenticated exploitation against default configurations of any WordPress site with the wpDataTables plugin installed at version 7.3.6 or below, per CVSS AV:N/AC:L/PR:N/UI:N. The only prerequisites are network reachability to the WordPress site and that wpDataTables is active (the vulnerable endpoint is exposed to anonymous visitors). Limiting factors: the site must actually be running an affected version of this specific plugin; the impact scope (which tables and columns are reachable) depends on what data sources the site administrator has configured wpDataTables to query, and the database account's privileges constrain whether the injection is read-only or can be escalated to writes/file operations.

Impact

All available signals point to genuine high priority: CVSS 9.3 with AV:N/AC:L/PR:N/UI:N means a remote, unauthenticated, low-complexity attack with no user interaction, and the S:C (scope change) reflects database access crossing the plugin's authorization boundary into broader WordPress data. The C:H/I:N/A:L impact profile is consistent with a read-oriented SQLi (data exfiltration via UNION or error/blind techniques) rather than arbitrary write - though depending on database privileges of the WordPress user, INTO OUTFILE or stacked-query escalation may still be possible. EPSS and KEV status are not provided in the input, so probabilistic exploitation likelihood and confirmed in-the-wild use cannot be assessed from this data; given Patchstack's track record of disclosing widely scanned WordPress plugin issues and that no public exploit identified at time of analysis, defenders should assume opportunistic mass scanning will follow disclosure within days to weeks.

Exploit ScenarioDerived

An attacker locates a public WordPress site running wpDataTables ≤ 7.3.6 (fingerprintable via /wp-content/plugins/wpdatatables/ asset paths) and sends a crafted HTTP request to a vulnerable AJAX/REST endpoint with a SQL payload in a table, filter, or sort parameter. They use UNION-based or time-based blind injection to enumerate wp_users and dump administrator password hashes and email addresses, then crack the hashes offline or pivot to wp_options to steal API keys and integration secrets. No authentication, user interaction, or social engineering is required.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 16, 2026

SQL injection in the wpDataTables WordPress plugin versions 7.3.6 and earlier allows unauthenticated remote attackers to inject crafted SQL into backend database queries, with CVSS 9.3 reflecting a scope-changed impact that reaches beyond the plugin's own data context. The CVSS vector indicates high confidentiality impact and low availability impact with no integrity impact, suggesting the flaw is primarily useful for extracting sensitive WordPress data (including credentials and PII) rather than tampering with records. No public exploit identified at time of analysis, but Patchstack's disclosure and the unauthenticated network attack vector make this a high-priority issue for any site running the plugin.

RemediationAI

Upstream fix available (PR/commit); released patched version not independently confirmed from the provided data - administrators should consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/wpdatatables/vulnerability/wordpress-wpdatatables-plugin-7-3-6-sql-injection-vulnerability) and the TMS Plugins changelog to identify and install the first version above 7.3.6 that contains the fix. Until upgrade is verified, compensating controls include placing a WAF rule (Wordfence, Patchstack mitigation, or ModSecurity OWASP CRS rules 942xxx) in front of wpDataTables AJAX endpoints to block SQL meta-characters in table, filter, and sort parameters - trade-off is potential false positives on legitimate table filter strings containing quotes. Alternatively, deactivate the wpDataTables plugin entirely, which removes the attack surface but breaks any front-end tables/charts it renders. As a defense-in-depth measure, restrict the database user used by WordPress to the minimum privileges needed (no FILE, no SUPER) so that a successful injection cannot escalate to file write or stacked-query abuse.

Affected VersionsENISA

wpDataTables n/a ≤7.3.6

Affected Packages

euvd wpdatatables no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

wpDataTables is a popular commercial WordPress plugin by TMS Plugins (CPE cpe:2.3:a:tms:wpdatatables) used to build interactive tables, charts, and dashboards backed by SQL queries against the WordPress database or external MySQL sources. CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) indicates that user-controllable input - likely a table identifier, filter, sort, or search parameter exposed via a public-facing AJAX or REST endpoint - is concatenated into a SQL statement without proper parameterization or escaping. Because wpDataTables routinely queries the WordPress core database to render front-end tables, an injection point gives an attacker direct read access to wp_users (password hashes, emails), wp_options (secrets, API keys), and any custom tables the plugin is configured to expose.

Know when Wpdatatables gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 9.3 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
vuln.today AI 9.3 CRITICAL

Unauthenticated network-reachable SQLi (AV:N/AC:L/PR:N/UI:N); scope changes to the WordPress DB (S:C); read-oriented data exposure drives C:H, no integrity change, minor A:L from query load.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

DescriptionCVE.org

Unauthenticated SQL Injection in wpDataTables <= 7.3.6 versions.

Executive ViewAI

Why It Matters

wpDataTables WordPress plugin (versions 7.3.6 and earlier) contains a critical SQL injection vulnerability allowing unauthenticated attackers to extract credentials and PII directly from WordPress databases. Any organization using this plugin faces immediate data breach risk and potential regulatory violations under GDPR, HIPAA, and PCI-DSS. With no patch currently available, urgent interim mitigation is required.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Plugin removal if operationally feasible; (2) Web Application Firewall rules with signatures blocking SQL injection payloads against the plugin's endpoints; (3) Database-level privilege restrictions limiting the plugin user account to minimum required tables and operations; (4) Enhanced logging and real-time alerting on database queries for anomalous patterns or large result sets; (5) Network segmentation isolating affected WordPress instances; (6) Active monitoring of WordPress.org plugin security advisories and Patchstack feeds for patch notifications.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

CVE-2021-26754 CRITICAL POC
9.8 Feb 08

wpDataTables before 3.4.1 mishandles order direction for server-side tables, aka admin-ajax.php?action=get_wdtable order

CVE-2014-9175 HIGH POC
7.5 Dec 02

SQL injection vulnerability in wpdatatables.php in the wpDataTables plugin 1.5.3 and earlier for WordPress allows remote

CVE-2023-4314 HIGH POC
7.2 Sep 11

The wpDataTables WordPress plugin before 2.1.66 does not validate the "Serialized PHP array" input data before deseriali

CVE-2021-24198 HIGH
8.1 Apr 12

The wpDataTables - Tables & Table Charts premium WordPress plugin before 3.4.2 has Improper Access Control. Rated high s

CVE-2021-24197 HIGH
8.1 Apr 12

The wpDataTables - Tables & Table Charts premium WordPress plugin before 3.4.2 has Improper Access Control. Rated high s

CVE-2026-57672 HIGH
7.1 Jul 02

Reflected/stored cross-site scripting in the wpDataTables WordPress plugin (versions 6.5.1.1 and earlier) allows unauthe

CVE-2026-65509 HIGH
7.1 Aug 06

Unauthenticated cross-site scripting in wpDataTables WordPress plugin (versions up to and including 7.5.1) allows remote

CVE-2026-66597 HIGH
7.1 Aug 20

Unauthenticated Cross-Site Scripting in the wpDataTables WordPress plugin (versions 6.5.1.4 and below) allows a remote,

CVE-2021-24200 MEDIUM
6.5 Apr 12

The wpDataTables - Tables & Table Charts premium WordPress plugin before 3.4.2 allows a low privilege authenticated user

CVE-2021-24199 MEDIUM
6.5 Apr 12

The wpDataTables - Tables & Table Charts premium WordPress plugin before 3.4.2 allows a low privilege authenticated user

CVE-2024-0591 MEDIUM
6.1 Mar 13

The wpDataTables - WordPress Data Table, Dynamic Tables & Table Charts Plugin plugin for WordPress is vulnerable to Refl

CVE-2023-23876 MEDIUM
5.4 May 03

Auth. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. No vendor pat

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy