CVE-2026-27373
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Essekia Tablesome tablesome allows Blind SQL Injection.This issue affects Tablesome: from n/a through <= 1.2.3.
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 · moderate confidenceThe Tablesome WordPress plugin (version <= 1.2.3) contains a blind SQL injection vulnerability due to improper neutralization of special elements in SQL commands. An attacker can inject malicious SQL queries through unsanitized input parameters to extract sensitive data from the database or cause denial of service.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Tablesome plugin installationNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Tablesome' in the list, or check the /wp-content/plugins/ directory for the tablesome folder.Affected if The Tablesome plugin is found installed on the WordPress site.
-
Identify installed Tablesome versionIn WordPress admin, go to Plugins > Installed Plugins > Tablesome, or check the main plugin file (tablesome.php) for the 'Version' header comment, or query the wp_options table for the 'tablesome_version' option.Affected if The installed version is unknown, unpatched, or falls within an affected version range.
-
Verify Tablesome plugin is activeCheck the Plugins page in WordPress admin to confirm Tablesome shows as 'Active', or query the wp_options table where option_name='active_plugins' and the result contains 'tablesome'.Affected if The Tablesome plugin is currently active on the site.
-
Check for Tablesome forms or public endpointsLook for published Tablesome forms or tables on the site, check for any frontend pages using Tablesome shortcodes, or review the site's public-facing URLs for tablesome-related parameters.Affected if Any Tablesome forms, tables, or public-facing features that accept user input are accessible on the site.
A WordPress site is affected if it has the Tablesome plugin installed, active, and exposes any Tablesome forms or input-handling features to users, particularly when the version is unpatched.
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 Tablesome to the latest patched version. If no update is available, implement strict input validation and convert vulnerable SQL queries to use parameterized queries (prepared statements).
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27373 — 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-27373 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