Woocommerce Support Ticket SystemWordPress extension · Vanquish
CVE-2024-13775
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 · uneditedThe WooCommerce Support Ticket System plugin for WordPress is vulnerable to unauthorized access and loss of data due to missing capability checks on the 'ajax_delete_message', 'ajax_get_customers_partial_list', and 'ajax_get_admins_list' functions in all versions up to, and including, 17.8. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary posts, and read names, emails, and capabilities of all users.
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 · moderate confidenceThe WooCommerce Support Ticket System plugin lacks proper capability/authorization checks on three AJAX functions (ajax_delete_message, ajax_get_customers_partial_list, ajax_get_admins_list), allowing any authenticated user with Subscriber-level access or higher to delete arbitrary posts and enumerate user information including names, emails, and capabilities.
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
< 17.9CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installation and versionNavigate to WordPress admin > Plugins and locate 'Vanquish Woocommerce Support Ticket System' in the installed plugins list. Check the version number displayed in the plugin details.Affected if The installed version is below 17.9 (e.g., 17.8, 17.7, etc.) or if the version is not explicitly shown and the plugin has not been recently updated.
-
Verify user role configurationGo to WordPress admin > Users > Users List. Review the existing user accounts and note their assigned roles.Affected if Any user account exists with the Subscriber role or higher (Subscriber, Contributor, Author, Editor, or Administrator). The vulnerability allows any authenticated user at Subscriber level to exploit the flaw.
-
Check for active user sessionsReview the WordPress user database or user management plugin to identify active or recently active user accounts with Subscriber-level access or above.Affected if There is at least one active or recently active user account assigned a role of Subscriber or higher.
-
Identify AJAX endpoint accessibilityInspect the plugin files (typically in wp-content/plugins/woocommerce-support-ticket-system/) for the AJAX handlers named ajax_delete_message, ajax_get_customers_partial_list, and ajax_get_admins_list. Check if these endpoints are registered with WordPress add_action('wp_ajax_...').Affected if These three AJAX functions are present in the plugin code and are registered without capability checks (no current_user_can() or similar authorization verification).
The environment is affected if the plugin version is below 17.9 and at least one user account with Subscriber-level or higher access exists on the WordPress site.
Generated from the published advisory. Verify against your own configuration.
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 · scoped17.9
Update the plugin to version 17.9 or later which includes proper capability checks; if no patched version is available, remove or disable the plugin until a fix is released.
WooCommerce Support Ticket System version 17.9
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the WooCommerce Support Ticket System plugin
- Click 'Update Now' if an update is available, or manually update to version 17.9
- Verify the plugin version shows 17.9 or higher after updating
- Confirm the update was successful by checking the plugin page
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
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-13775 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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