dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-12089

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Data Tables Generator by Supsystic plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the cleanCache() function in all versions up to, and including, 1.10.45. This makes it possible for authenticated attackers, with Administrator-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

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 Data Tables Generator by Supsystic WordPress plugin contains an arbitrary file deletion vulnerability in the cleanCache() function due to insufficient path validation. Authenticated administrators can manipulate file paths to delete arbitrary files on the server, including critical files like wp-config.php, enabling potential remote code execution.

MitigationUpdate the plugin to version 1.10.46 or later which includes proper path validation. Until updated, restrict administrator access and implement WAF rules to block suspicious file deletion requests.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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. Locate the installed plugin version
    Access the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Find 'Data Tables Generator by Supsystic' and note the version number displayed. Alternatively, check the plugin's main PHP file (usually in wp-content/plugins/tables-generator-by-supsystic/) for the version header in the file comments, or inspect the readme.txt file for the 'Stable tag' entry.
    Affected if The installed version is lower than 1.10.46, or the version cannot be determined (plugin is present but version info is missing or inaccessible).
  2. Verify the cleanCache function exists
    Locate the plugin's PHP files, typically in wp-content/plugins/tables-generator-by-supsystic/. Search for the function definition 'function cleanCache' within the plugin files. This function is where the arbitrary file deletion vulnerability resides.
    Affected if The cleanCache function exists in the plugin code, indicating the vulnerable code path is present regardless of whether it has been accessed.
  3. Inspect server access logs for cleanCache requests
    Review web server access logs (Apache error.log, Nginx access.log, or WP debug logs if enabled) for requests containing 'cleanCache' or 'action=cleanCache' in the URI or POST parameters. Look for patterns like '/wp-admin/admin-ajax.php?action=cleanCache' or similar endpoint variations.
    Affected if Any logs show requests to the cleanCache function, especially with unusual file path parameters that suggest attempts to delete files outside the intended cache directory.
  4. Check critical WordPress files for modification or deletion
    Verify the integrity of wp-config.php and other critical configuration files in the WordPress root directory. Compare file hashes or timestamps against known-good backups. Check if wp-config.php exists and is readable.
    Affected if wp-config.php is missing, has unexpected modifications, or the site is prompting for a new installation (indicating wp-config.php was deleted).

The environment is affected if the Data Tables Generator by Supsystic plugin is installed with a version lower than 1.10.46, or if logs show suspicious cleanCache requests, or if critical files like wp-config.php have been altered or deleted.

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 the plugin to version 1.10.46 or later which includes proper path validation. Until updated, restrict administrator access and implement WAF rules to block suspicious file deletion requests.

Recommended fix Moderate confidence

1.10.46 or later

  1. Update the Data Tables Generator by Supsystic plugin to the latest available version (1.10.46 or later)
  2. Verify the update was successful by checking the plugin version in WordPress admin > Plugins
  3. Confirm the cleanCache() function no longer allows path traversal by testing with a non-cache directory path

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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