dbcve.org
Woocommerce Support Ticket SystemWordPress extension · Vanquish

CVE-2024-10627

CRITICAL · 9.8 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 uploads due to missing file type validation in the ajax_manage_file_chunk_upload() function in all versions up to, and including, 17.7. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 lacks file type validation in its ajax_manage_file_chunk_upload() function, allowing unauthenticated attackers to upload arbitrary files including executable scripts to the server. This arbitrary file upload vulnerability with CVSS 9.8 enables remote code execution by uploading malicious PHP files or other dangerous content types.

MitigationUpdate the WooCommerce Support Ticket System plugin to version 17.8 or later which includes proper file type validation. If immediate update is not possible, consider disabling the affected plugin or implementing web application firewall rules to block unauthorized file uploads.

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
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. Verify the plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the 'woocommerce-support-ticket-system' folder, or view the installed plugins list in the WordPress admin dashboard under Plugins.
    Affected if The plugin folder exists in the plugins directory or appears in the WordPress admin plugins list.
  2. Determine the installed plugin version
    Open the main plugin PHP file (e.g., woocommerce-support-ticket-system.php) and locate the version header comment at the top, or view the version in the WordPress admin plugins list.
    Affected if The version number is lower than 17.8 (for example, 17.7, 17.6, or any version below 17.8).
  3. Confirm the vulnerable AJAX endpoint exists
    Check if the WordPress AJAX handler responds to the plugin's upload action. Examine the plugin's JavaScript files or AJAX registration code for the action name 'manage_file_chunk_upload' or similar, then test if the endpoint /wp-admin/admin-ajax.php?action=manage_file_chunk_upload is accessible.
    Affected if The AJAX endpoint responds to requests (including unauthenticated requests) and processes file uploads without proper validation.
  4. Inspect the uploads directory for suspicious files
    Review the wp-content/uploads/ directory (or custom upload path) for recently added files with dangerous extensions such as .php, .phtml, .phar, .exe, .js, or .sh, especially in ticket-related subdirectories.
    Affected if Unexpected executable or script files are found in upload directories, particularly PHP files that were not intentionally uploaded by administrators.

You are affected if the WooCommerce Support Ticket System plugin is installed with a version below 17.8 and the file upload AJAX functionality is exposed and accessible without authentication.

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 which includes proper file type validation. If immediate update is not possible, consider disabling the affected plugin or implementing web application firewall rules to block unauthorized file uploads.

Recommended fix High confidence

version 17.8

  1. Update the WooCommerce Support Ticket System plugin to version 17.8 or the latest available version through the WordPress plugin administration panel
  2. Verify the update was successful by checking the plugin version
  3. If possible, verify that file upload functionality is restricted to expected file types only

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.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-10627 — 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-10627 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