dbcve.org
Store Toolkit For WoocommerceWordPress extension · Visser

CVE-2016-10923

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 1.5.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-store-toolkit plugin before 1.5.8 for WordPress has privilege escalation.

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-store-toolkit WordPress plugin before version 1.5.8 contains a privilege escalation vulnerability that allows authenticated users (or potentially unauthenticated attackers) to gain elevated administrative privileges on WordPress sites running this plugin.

MitigationUpdate the woocommerce-store-toolkit plugin to version 1.5.8 or later immediately. Audit user accounts and logs for suspicious privilege escalation activity since the vulnerability was disclosed.

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
Store Toolkit For WoocommerceWordPress extension
Affected:< 1.5.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.0/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. Locate the woocommerce-store-toolkit plugin
    Check your WordPress installation's wp-content/plugins/ directory for a folder named 'woocommerce-store-toolkit' or a folder matching 'visser-store-toolkit-for-woocommerce' or similar Visser Labs naming conventions
    Affected if The plugin folder exists in your plugins directory
  2. Identify the installed plugin version
    Open the main plugin PHP file (typically named the same as the plugin folder) and locate the version comment in the plugin header, or check the readme.txt file for the 'Stable tag' version entry
    Affected if You cannot locate a version number or the version is below 1.5.8
  3. Verify the plugin is active
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or query the wp_options table for option_name='active_plugins' to confirm the plugin is currently enabled
    Affected if The plugin is listed as active on your site
  4. Confirm the vulnerability scope
    Review the CVE description - this is a privilege escalation vulnerability that allows authenticated users to gain administrative privileges. Check if user registration or contributor-level accounts exist on your site
    Affected if Your site allows user registration or has subscriber/contributor accounts, and the vulnerable plugin version is installed and active

You are affected if the woocommerce-store-toolkit (or Visser Store Toolkit For Woocommerce) plugin is installed, active, and the version is below 1.5.8.

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 1.5.8 or later
Fixed in 1.5.8
Interim mitigation

Update the woocommerce-store-toolkit plugin to version 1.5.8 or later immediately. Audit user accounts and logs for suspicious privilege escalation activity since the vulnerability was disclosed.

Recommended fix High confidence

1.5.8

  1. Log into the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Store Toolkit For WooCommerce' in the plugin list
  4. Check if an update is available (if not, manually download version 1.5.8 or later from wordpress.org)
  5. Click 'Update Now' to install version 1.5.8 or newer
  6. Alternatively, update via WP-CLI: wp plugin update woocommerce-store-toolkit
  7. Verify the plugin version after update to confirm 1.5.8 or later is installed
  8. Test that administrative functions work correctly

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

Fix this in Store Toolkit For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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