Security readout for executives and security teams
Plain-English summary
CVE-2026-27373 is a high-severity SQL injection issue in the WordPress Tablesome plugin through version 1.2.3. An authenticated user with low privileges may be able to make the site’s database answer unintended queries. This can expose sensitive data and may affect site availability. No active exploitation is cited in the provided sources.
Executive priority
Treat this as a high-priority WordPress plugin risk where Tablesome is deployed. The main business concern is database confidentiality loss from authenticated access. Prioritize public-facing or customer-account-enabled WordPress sites first, while confirming vendor remediation because the provided sources do not name a fixed version.
Technical view
The issue is CWE-89 blind SQL injection in Essekia Tablesome for WordPress, affecting versions up to 1.2.3 per the CVE description. CVSS 3.1 is 8.5 with network access, low attack complexity, low privileges required, no user interaction, changed scope, high confidentiality impact, no integrity impact, and low availability impact.
Likely exposure
Exposure is limited to WordPress sites running the Tablesome plugin at version 1.2.3 or earlier. The CVSS vector indicates exploitation requires a low-privileged authenticated account, not anonymous access. Public source details do not identify exact vulnerable parameters or deployment conditions.
Exploitation context
The sources describe blind SQL injection but do not state active exploitation, public exploit availability, or inclusion in CISA KEV. Because WordPress plugins are commonly internet-facing, vulnerable sites with user registration or multiple low-privileged accounts should be prioritized for review.
Researcher notes
Evidence is limited to CVE metadata and Patchstack’s vulnerability entry. Do not assume unauthenticated exploitability; the CVSS vector specifies PR:L. The record lists Tablesome through 1.2.3, but the structured affected data is sparse. Validate against vendor and plugin repository information before broad claims.
Mitigation direction
- Inventory WordPress sites for the Tablesome plugin and installed version.
- If version is 1.2.3 or earlier, check vendor or Patchstack guidance immediately.
- Update, disable, or remove the plugin if vendor guidance recommends it.
- Restrict unnecessary low-privileged WordPress accounts on affected sites.
- Monitor database and WordPress logs for suspicious authenticated activity.
Validation and detection
- Confirm whether Tablesome is installed on each WordPress instance.
- Record the installed plugin version and compare it with 1.2.3.
- Review vendor, WordPress plugin, or Patchstack pages for fixed-version information.
- Check whether untrusted users can authenticate to affected sites.
- Look for unusual database errors or abnormal queries tied to low-privileged accounts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupDatabase 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 lookupCVE-2026-27373 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L3.14.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.5HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.