Woocommerce Customers ManagerWordPress extension · Vanquish
CVE-2024-13343
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 Customers Manager plugin for WordPress is vulnerable to Privilege Escalation due to a missing capability check on the ajax_assign_new_roles() function in all versions up to, and including, 31.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to elevate their privileges to that of an administrator.
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 confidenceThe WooCommerce Customers Manager plugin for WordPress has a privilege escalation vulnerability in versions up to 31.3. The ajax_assign_new_roles() function lacks a capability check, allowing any authenticated user with Subscriber-level access or higher to call this function and assign themselves Administrator privileges.
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 Customers ManagerWordPress extension
< 31.4CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find 'WooCommerce Customers Manager' (or 'Vanquish Woocommerce Customers Manager'). The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header or version.php for the Version constant.Affected if The installed version is lower than 31.4 (e.g., 31.3, 31.2, etc.)
-
Locate the vulnerable functionAccess the WordPress site files via FTP or file manager. Navigate to /wp-content/plugins/woocommerce-customers-manager/ and search for the function ajax_assign_new_roles() in PHP files, typically in includes/class-ajax.php or similar ajax handler files.Affected if The ajax_assign_new_roles() function exists in the plugin files and is accessible without admin-level capability verification
-
Verify missing capability checkOpen the file containing ajax_assign_new_roles() and examine the function code. Look for current_user_can() or similar permission checks at the function start. The vulnerability exists if no capability check (such as current_user_can('manage_options')) is present before role assignment logic.Affected if The function contains no current_user_can() validation or equivalent capability check before processing role assignments
-
Confirm user role configurationIn WordPress admin, go to Users > Roles (or use a role editor plugin) to list existing roles. Check if any roles with Subscriber-level access or higher exist on the site.Affected if Any user role with Subscriber access or higher exists, meaning authenticated users can access the vulnerable function
-
Test function accessibility (if safe to do so)Using browser developer tools or a tool like curl, examine if the wp_ajax_woocommerce_customers_manager_assign_new_roles AJAX action is registered and callable. Check wp-content/plugins/woocommerce-customers-manager/woocommerce-customers-manager.php for add_action('wp_ajax_...', 'ajax_assign_new_roles') calls.Affected if The AJAX action is registered and callable by authenticated users (any logged-in user)
Your environment is affected if the WooCommerce Customers Manager plugin version is below 31.4 AND the ajax_assign_new_roles() function is present without a capability check, allowing any logged-in user with Subscriber-level access to escalate privileges to Administrator.
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 · scoped31.4
Update the WooCommerce Customers Manager plugin to version 31.4 or later. If immediate update is not possible, implement a capability check (current_user_can('manage_options')) on the ajax_assign_new_roles() function as a temporary workaround.
31.4
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate WooCommerce Customers Manager plugin
- Check if an update is available and apply it
- Verify the plugin version is 31.4 or higher after update
- Confirm the update was successful
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Woocommerce Customers Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13343 — 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-13343 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