Tablesome Table – Contact Form DB – WPForms, CF7, Gravity, Forminator, Fluent <= 1.1.32 - Unauthenticated Arbitrary File Upload
Strategic Overview
- Status
- Patched in 1.3.33
- Affected Version
<= 1.1.32- CVSS
- 9.8Critical
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2025-11499
At a glance
CVE-2025-11499 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Tablesome Table WordPress plugin, affecting versions <= 1.1.32. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.3.33; sites on affected versions should update now. Disclosed October 2025, reported by Talal Nasraddeen.
Vulnerability Overview
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.
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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
Tablesome Table <= 1.1.32 carries this weakness at set_featured_image_from_external_url(), and reaching it takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Tablesome Table the fix is 1.3.33: builds <= 1.1.32 are affected, anything from 1.3.33 onward is not.
Remediation
Update to version 1.3.33, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Tablesome Table 1.3.33 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Other vulnerabilities in Tablesome Table – Contact Form DB – WPForms, CF7, Gravity, Forminator, Fluent
- 8.8CVE-2025-12845: Tablesome Table Authenticated (Subscriber+)
CVE-2025-12845 - 7.5CVE-2026-66659: Tablesome Table SQL Injection
CVE-2026-66659 - 6.5CVE-2026-27373: Tablesome Table SQL Injection
CVE-2026-27373 - 6.5CVE-2025-68516: Tablesome <= 1.1.35.1 Information Exposure
CVE-2025-68516 - 6.3CVE-2022-4974: Freemius SDK <= 2.4.2 Missing Authorization Checks
CVE-2022-4974 - 6.1CVE-2024-13362: Freemius <= 2.10.1 Reflected DOM-Based XSS
CVE-2024-13362 - 6.1CVE-2024-29110: Table & Contact Form 7 Database Reflected XSS
CVE-2024-29110 - 6.1CVE-2023-33999: Freemius SDK <= 2.5.9 Reflected Cross-Site Scripting
CVE-2023-33999
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C