CVE-2026-49080
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 · uneditedUnauthenticated SQL Injection in wpDataTables <= 7.3.6 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 confidenceAn unauthenticated SQL Injection vulnerability exists in the wpDataTables WordPress plugin versions 7.3.6 and below. The vulnerability allows remote attackers to inject malicious SQL queries through unspecified input parameters without requiring any authentication, potentially leading to unauthorized data access or database compromise.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate wpDataTables plugin installationCheck the WordPress plugins directory (wp-content/plugins) for the wpdatatables folder, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins';Affected if The wpdatatables folder exists or the plugin is in the active plugins list
-
Determine installed wpDataTables versionCheck the plugin header in wp-content/plugins/wpdatatables/wpdatatables.php for the 'Version' field, or query: SELECT meta_value FROM wp_postmeta WHERE meta_key = 'version' AND post_id IN (SELECT ID FROM wp_posts WHERE post_type = 'plugin');Affected if The version is 7.3.6 or lower (e.g., 7.3.6, 7.3.5, 7.3.0, etc.)
-
Verify plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm wpDataTables shows as 'Active', or check if it appears in the active_plugins optionAffected if The plugin is currently active and version 7.3.6 or below
-
Inspect web server access logs for SQL injection indicatorsReview Apache/nginx access logs (typically in /var/log/apache2/ or /var/log/nginx/) for requests to wpDataTables endpoints containing SQL keywords (UNION, SELECT, INSERT, DROP, --, or encoded variations)Affected if Suspicious SQL-like patterns are found in requests to wpDataTables-related URLs
You are affected if wpDataTables plugin version 7.3.6 or below is installed and active in your WordPress environment, particularly if web logs show SQL injection attempts targeting the plugin.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate wpDataTables to the latest version beyond 7.3.6 to patch the SQL injection vulnerability. As an immediate workaround, restrict web server access to the affected endpoint and monitor logs for suspicious SQL-like patterns.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-49080 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49080 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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