LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24524: WordPress Tablesome plugin <= 1.2.8 - Broken Access Control vulnerability

Missing Authorization vulnerability in Essekia Tablesome tablesome allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Tablesome: from n/a through <= 1.2.8.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24524 is a broken access control issue in the WordPress Tablesome plugin. A logged-in user may be able to perform an action they should not be authorized to perform. The public record rates it medium severity, with limited integrity impact and no stated confidentiality or availability impact.

Executive priority

Treat as a routine but timely WordPress plugin risk. Prioritize sites with public registration, many contributors, or business-critical tables. There is no sourced evidence of active exploitation, but access-control flaws can cause unauthorized content or data changes.

Technical view

The issue is CWE-862 Missing Authorization in Essekia Tablesome through version <= 1.2.8, per the CVE description. CVSS 3.1 is 4.3: network reachable, low attack complexity, low privileges required, no user interaction, and low integrity impact only.

Likely exposure

Exposure is limited to WordPress sites with the Tablesome plugin installed, especially versions at or below 1.2.8. The attacker must already have a low-privileged account, reducing broad internet risk but increasing concern on sites with open registration or many users.

Exploitation context

No CISA KEV listing or provided source indicates active exploitation. Public details are limited. The CVSS vector indicates exploitation requires authentication but not user interaction, and the expected impact is unauthorized modification rather than data theft or service outage.

Researcher notes

Evidence is sparse. The CVE states affected versions through <= 1.2.8, while the Patchstack URL slug appears to reference a different version string. The structured affected data is not detailed. Validate against vendor and Patchstack records before making final remediation decisions.

Mitigation direction

  • Identify all WordPress sites using the Tablesome plugin.
  • Check vendor, WordPress, or Patchstack guidance for a fixed version.
  • Update Tablesome when an official patched release is available.
  • Disable Tablesome if not business-critical and no fix is available.
  • Limit WordPress account creation and remove unnecessary low-privileged users.

Validation and detection

  • Inventory installed Tablesome versions across WordPress environments.
  • Flag Tablesome versions at or below 1.2.8 for review.
  • Review WordPress users, roles, and registration settings.
  • Monitor plugin changelogs and vendor advisories for authorization fixes.
  • Check logs for unexpected Tablesome-related changes by low-privileged users.
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-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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
cve · low confidence lookup

CVE-2026-24524 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
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

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
0Timeline events
0ADP providers
2Source links

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-24524Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
EssekiaTablesometablesome, 0unaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.