CVE-2025-68516

Tablesome <= 1.1.35.1 - Authenticated (Subscriber+) Information Exposure

2025-12-22 00:00
daroo

Strategic Overview

Status
Patched in 1.1.35.2
Affected Version
<= 1.1.35.1
CVSS
6.5Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-68516
View all Tablesome Table – Contact Form DB – WPForms, CF7, Gravity, Forminator, Fluent vulnerabilities

At a glance

CVE-2025-68516 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Tablesome Table WordPress plugin, affecting versions <= 1.1.35.1. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.1.35.2; sites on affected versions should update now. Disclosed December 2025, reported by daroo.

Vulnerability Overview

The Tablesome Table – Contact Form DB – WPForms, CF7, Gravity, Forminator, Fluent plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.1.35.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract sensitive user or configuration data.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Tablesome Table <= 1.1.35.1 takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Tablesome Table the fix is 1.1.35.2: builds <= 1.1.35.1 are affected, anything from 1.1.35.2 onward is not.

Remediation

Update to version 1.1.35.2, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Tablesome Table 1.1.35.2 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C