dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-11499

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
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 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 · high confidence

The Tablesome WordPress plugin up to version 1.1.32 contains an unauthenticated arbitrary file upload vulnerability in the set_featured_image_from_external_url() function. The function fails to validate file types, allowing attackers to upload any file type to the server. When a workflow trigger exists and unauthenticated users can add featured images, this can lead to remote code execution.

MitigationImmediately update the Tablesome plugin to version 1.1.33 or later. If immediate patching is not possible, disable any workflows that allow external URL featured images for unauthenticated users, and consider restricting upload capabilities at the server level.

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
High
Integrity
High
Availability
High

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

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. Check Tablesome plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find Tablesome. The version number is displayed under the plugin name. Alternatively, check the plugin header in /wp-content/plugins/tablesome/includes/class-tablesome.php for 'Version:' value.
    Affected if Version is 1.1.32 or lower.
  2. Verify if any Tablesome workflows exist
    In WordPress admin, go to Tablesome > Workflows (or similar menu item). Look for any workflow entries in the database table wp_tablesome_workflows if the menu is not accessible.
    Affected if Any workflow exists in the Tablesome plugin.
  3. Inspect workflow triggers for external URL featured image
    Examine the workflow configuration for a trigger that allows 'set_featured_image_from_external_url' or similar external URL image functionality. Check workflow settings in the database or through the Tablesome UI if available.
    Affected if A workflow trigger exists that allows setting featured images from external URLs.
  4. Check if unauthenticated users can submit external URL images
    Review the workflow permissions or test submitting a request without authentication. Inspect the workflow access controls in the Tablesome workflow settings or database to verify public/external access is permitted.
    Affected if Unauthenticated (logged-out) users have permission to trigger the external URL featured image feature.

A user is affected if their Tablesome plugin version is 1.1.32 or lower AND a workflow exists that allows unauthenticated users to set featured images from external URLs.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately update the Tablesome plugin to version 1.1.33 or later. If immediate patching is not possible, disable any workflows that allow external URL featured images for unauthenticated users, and consider restricting upload capabilities at the server level.

Recommended fix Moderate confidence

Version 1.1.33 or later from the WordPress plugin repository

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Tablesome Table – Contact Form DB' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 1.1.33 or later from the WordPress plugin repository
  5. Verify the installed version is 1.1.33 or higher after updating

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11499 — 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-11499 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