dbcve.org
Woocommerce Support Ticket SystemWordPress extension · Vanquish

CVE-2024-10625

CRITICAL · 9.1 CVSS v3.1 Published 2024-11-09
Fix available
A fix is available. Upgrade to 17.8 or later.
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 WooCommerce Support Ticket System plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_tmp_uploaded_file() function in all versions up to, and including, 17.7. This makes it possible for unauthenticated attackers 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 WooCommerce Support Ticket System plugin for WordPress versions up to 17.7 contains an arbitrary file deletion vulnerability in the delete_tmp_uploaded_file() function. The function lacks proper path validation, allowing unauthenticated attackers to use path traversal sequences (e.g., ../../wp-config.php) to delete any file on the server. Deleting critical files like wp-config.php enables remote code execution by triggering WordPress reinstallation.

MitigationUpdate the WooCommerce Support Ticket System plugin to version 17.8 or later immediately. If immediate updating is not possible, disable the plugin until a patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Woocommerce Support Ticket SystemWordPress extension
Affected:< 17.8

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify WordPress installation exists
    Check for wp-config.php in the document root using file_exists() or by listing directory contents
    Affected if wp-config.php exists, indicating a WordPress installation that could be affected if the plugin is present
  2. Identify if WooCommerce Support Ticket System plugin is installed
    Look for the plugin directory at wp-content/plugins/woocommerce-support-ticket-system or check via WordPress admin plugin list
    Affected if The plugin directory or entry exists in the plugins folder
  3. Check installed plugin version
    Read the main plugin file header (e.g., woocommerce-support-ticket-system.php) and look for the Version: field, or query the WordPress database wp_options table for the option_name containing the plugin version
    Affected if The version number found is less than 17.8 (e.g., 17.7, 17.6, etc.)
  4. Confirm plugin is active
    Check the WordPress database wp_options table for active_plugins option, or use wp-cli plugin status command if available
    Affected if The plugin appears in the list of active plugins

A WordPress site with the WooCommerce Support Ticket System plugin installed, active, and running a version below 17.8 is vulnerable to unauthenticated arbitrary file deletion via path traversal in the delete_tmp_uploaded_file() function.

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
Upgrade available Upgrade to 17.8 or later
Fixed in 17.8
Interim mitigation

Update the WooCommerce Support Ticket System plugin to version 17.8 or later immediately. If immediate updating is not possible, disable the plugin until a patch can be applied.

Recommended fix High confidence

version 17.8

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'WooCommerce Support Ticket System' plugin
  4. Click 'Update Now' or manually update to version 17.8
  5. Verify the plugin version shows 17.8 or later after updating

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

Fix this in Woocommerce Support Ticket System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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