dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-14610

HIGH · 7.2 CVSS v3.1 Published 2026-01-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/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
The TableMaster for Elementor plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.3.6. This is due to the plugin not restricting which URLs can be fetched when importing CSV data from a URL in the Data Table widget. This makes it possible for authenticated attackers, with Author-level access and above, to make web requests to arbitrary locations, including localhost and internal network services, and read sensitive files such as wp-config.php via the 'csv_url' parameter.

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 TableMaster for Elementor plugin for WordPress versions up to 1.3.6 contains an SSRF vulnerability in its Data Table widget's CSV import feature. The plugin accepts arbitrary URLs via the 'csv_url' parameter without validating or restricting the destination, allowing authenticated Author-level users to make the server fetch internal resources, access localhost/internal network services, and read sensitive files like wp-config.php.

MitigationUpdate to the latest version of TableMaster when available; until then, restrict user permissions to Subscriber or below, or temporarily disable the Data Table widget's CSV URL import functionality.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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. Verify TableMaster plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate TableMaster for Elementor. Check the version number displayed. Compare this version to the affected range (versions up to and including 1.3.6 are vulnerable).
    Affected if The installed version is 1.3.6 or lower.
  2. Identify active Data Table widgets
    In Elementor editor, search for any pages/posts containing the Data Table widget. Alternatively, query the WordPress postmeta table for meta_value containing 'tablemaster' or 'tm-data-table' elementor widget records.
    Affected if Any Data Table widget is present and active on the site.
  3. Confirm Author-level users exist
    Navigate to WordPress Users > All Users and review the role column. Count users assigned the Author role.
    Affected if At least one user with Author role exists on the site.
  4. Check CSV URL import configuration
    Edit any page containing a TableMaster Data Table widget, enter the widget settings, and look for CSV import options. Specifically check if a csv_url field or URL-based CSV import setting is available and save a test configuration.
    Affected if The CSV import feature is accessible and configurable (the vulnerability requires this feature to be present and configurable by Author users).

If the TableMaster plugin version is 1.3.6 or lower AND Author-level users exist on the site AND the Data Table widget's CSV import functionality is accessible, the environment is affected by this SSRF vulnerability.

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

Update to the latest version of TableMaster when available; until then, restrict user permissions to Subscriber or below, or temporarily disable the Data Table widget's CSV URL import functionality.

Recommended fix Moderate confidence

Latest version of TableMaster for Elementor (version higher than 1.3.6)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the TableMaster for Elementor plugin
  4. Check if an update is available (version higher than 1.3.6)
  5. If update available, click 'Update Now' to install the patched version
  6. If no update visible, manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the Data Table widget's CSV import functionality still works correctly
  8. Ensure only trusted users with Author-level access or higher are permitted on the site

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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