LiveActive security incident?Get immediate response
CVE Record

CVE-2026-66659: WordPress Tablesome Table plugin <= 1.2.9 - SQL Injection vulnerability

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Essekia Tablesome Table allows Blind SQL Injection. This issue affects Tablesome Table: from n/a through 1.2.9.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A critical flaw in the WordPress Tablesome Table plugin through version 1.2.9 may let an unauthenticated internet attacker extract database information through blind SQL injection. Exploitation requires no user action and may also cause limited service disruption. The supplied evidence does not indicate database modification impact.

Executive priority

Treat this as an urgent inventory and remediation issue for internet-facing WordPress systems. Prioritize sites holding sensitive customer, employee, authentication, or operational data. Escalate immediately where version 1.2.9 or earlier is active, while avoiding claims of compromise without supporting evidence.

Technical view

CVE-2026-66659 is a CWE-89 blind SQL injection vulnerability in Essekia Tablesome Table through 1.2.9. Its CVSS 3.1 score is 9.3: network-accessible, low complexity, unauthenticated, and requiring no user interaction. The vector assigns high confidentiality impact, no integrity impact, limited availability impact, and changed scope.

Likely exposure

WordPress sites running Tablesome Table version 1.2.9 or earlier are potentially exposed, particularly when reachable from the internet. The bundle does not identify the vulnerable endpoint, required plugin configuration, installation prevalence, or whether protective controls reliably block exploitation.

Exploitation context

The CVSS vector supports remote, unauthenticated, low-complexity exploitation without user interaction. However, the CVE is not listed as KEV in the supplied bundle, and no cited evidence here establishes active exploitation, public exploit availability, or observed attacks.

Researcher notes

The public bundle identifies blind SQL injection but does not provide the vulnerable parameter, route, root cause, patch commit, corrected version, or configuration prerequisites. Validate exposure defensively through version and activation checks. Do not infer active exploitation from severity alone; KEV is false in the supplied data.

Mitigation direction

  • Inventory WordPress sites and identify every installed Tablesome Table version.
  • Check current vendor or Patchstack guidance for a version explicitly confirmed unaffected.
  • Update to a confirmed unaffected release when authoritative guidance identifies one.
  • If no confirmed fix is available, disable or remove the affected plugin where operationally feasible.
  • Restrict external access to affected sites when temporary removal is not feasible.

Validation and detection

  • Confirm the plugin version and activation state on every WordPress deployment.
  • Verify any installed replacement version is explicitly documented as unaffected.
  • Review web and security logs for unusual requests targeting Tablesome functionality.
  • Review database monitoring for abnormal queries, errors, latency, or unexpected data access.
  • Confirm affected plugin code is inactive when using temporary disablement.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-66659 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.3CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L3.94.7Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

9.3Critical
CVSS 3.1 vector shape for CVE-2026-66659Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
EssekiaTablesome Tabletablesome, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.