dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-30944

HIGH · 7.5 CVSS v3.1 Published 2025-10-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authorization vulnerability in Essekia Tablesome Table Premium tablesome-premium allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Tablesome Table Premium: from n/a through <= 1.1.23.

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 confidence

The Tablesome Table Premium WordPress plugin versions up to 1.1.23 contains a missing authorization vulnerability allowing users to access functionality not properly constrained by access control lists (ACLs). An unauthenticated attacker can potentially execute privileged actions due to missing capability checks on certain functions.

MitigationUpgrade Tablesome Table Premium to a version beyond 1.1.23 that includes proper authorization checks. Until then, restrict access to the wp-admin directory or disable the plugin if possible.

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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Tablesome plugin directory
    Check the WordPress plugins folder at /wp-content/plugins/ for a folder named 'tablesome' or similar. List all installed plugins via wp-cli: wp plugin list --status=active
    Affected if The plugin folder exists and the plugin is active
  2. Identify the installed version
    Read the main plugin file header. In the tablesome plugin folder, open the primary PHP file (often tablesome.php or similar) and look for the 'Version' header comment, or query it via wp-cli: wp plugin get tablesome --field=version
    Affected if The version number is 1.1.23 or lower
  3. Verify the plugin is accessible to unauthenticated users
    Confirm the WordPress site allows public access. The vulnerability is exploitable by unauthenticated (not-logged-in) users, so if the site has open registration or allows guest access, the attack surface exists. No specific configuration toggle needs to be enabled for the flaw.
    Affected if The plugin is active and the site permits unauthenticated access to WordPress functionality

A user is affected if Tablesome Table Premium plugin is installed, active, and running version 1.1.23 or lower on a WordPress site that permits unauthenticated access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Tablesome Table Premium to a version beyond 1.1.23 that includes proper authorization checks. Until then, restrict access to the wp-admin directory or disable the plugin if possible.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30944 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30944 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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