Tablesome - Remote Code Execution (CVE-2025-11499)

CVE-2025-11499

Vulnerability CVE-2025-11499 PLUGIN tablesome CRITICAL

The Tablesome Table – Contact Form DB – WPForms, CF7, Gravity, Forminator, Fluent plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the set_featured_image_from_external_url() function in all versions up to, and including, 1.1.32. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible in configurations where unauthenticated users have been provided with a method for adding featured images, and the workflow trigger is created.

CVE-2025-11499

CRITICAL CVSS 9.8 Published 2025-11-01 Updated 2026-06-17

AI Risk Critical (100/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P1 Immediate

Severity Band CRITICAL

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

Affected Components 2

Reference Links 3

AI Risk Engine Critical (100/100)

Exploitability Very High

Active Exploitation No strong signal

Published Exploit Status No public exploit references

Threat Timeline

2025-11-01 CVE published and first recorded in the threat feed.
2026-06-17 Record updated with latest vulnerability metadata.
2026-04-09 AI technical context refreshed for mitigation and impact guidance.
Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 178 days ago

AI enriched 178 days ago (2026-04-09 07:19 UTC)

Technical Summary

Potential Impact

Severity is CRITICAL (CVSS 9.8). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Very High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Tablesome PLUGIN · tablesome Affected range not specified Fixed version not specified

Tablesome Table PLUGIN · tablesome-table Affected range not specified Fixed version not specified

References

What to do about this

Patch immediately Serious, and reachable without meaningful privilege.

Fix it

Update Tablesome to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Tablesome, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Tablesome. No account is needed to exploit this, so a public site is reachable by anyone.

How do I fix it?

Update Tablesome to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Remote Code Execution flaw. An attacker who exploits it can run their own code on the server, which is total control of the site.