dbcve.org
Woocommerce Support Ticket SystemWordPress extension · Vanquish

CVE-2024-10626

HIGH · 8.1 CVSS v3.1 Published 2024-11-09
Fix available
A fix is available. Upgrade to 17.8 or later.
See remediation →
87/100
Remediation priority · High
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 WooCommerce Support Ticket System plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_uploaded_file() function in all versions up to, and including, 17.7. This makes it possible for authenticated attackers, with Subscriber-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 WooCommerce Support Ticket System plugin for WordPress contains an arbitrary file deletion vulnerability in the delete_uploaded_file() function. Due to insufficient file path validation, authenticated attackers with Subscriber-level access can use path traversal techniques to delete arbitrary files on the server, including critical files like wp-config.php.

MitigationUpgrade to version 17.8 or later, which contains proper file path validation in the delete_uploaded_file() function to prevent path traversal attacks.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm the plugin is installed
    Check your WordPress installation for the Vanquish Woocommerce Support Ticket System plugin in the plugins directory
    Affected if The plugin is found installed on the WordPress site
  2. Identify the installed version
    Locate the plugin main file and check the version header comment, or use wp-cli: wp plugin list --name='woocommerce-support-ticket-system'
    Affected if The installed version is lower than 17.8
  3. Verify the vulnerable function exists
    Inspect the plugin files for the delete_uploaded_file() function, typically found in the plugin's main PHP file or includes directory
    Affected if The delete_uploaded_file function is present and contains file deletion logic without proper path validation
  4. Check for subscriber-level access
    Review WordPress user role settings and confirm if subscriber role exists or if user registration is enabled, as the vulnerability requires authenticated subscriber-level access
    Affected if Subscriber-level accounts can be created or already exist on the site

You are affected if the plugin is installed with a version below 17.8 and the delete_uploaded_file function is accessible to subscriber-level users.

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

Upgrade to version 17.8 or later, which contains proper file path validation in the delete_uploaded_file() function to prevent path traversal attacks.

Recommended fix High confidence

version 17.8

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WooCommerce Support Ticket System' plugin
  4. 4. Check the current installed version - if it is 17.7 or below, an update is required
  5. 5. If an update is available, click 'Update Now' to install version 17.8
  6. 6. Alternatively, download version 17.8 from the official source (codecanyon.net) and upload it via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the new version number reflects 17.8

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
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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