dbcve.org
Store Toolkit For WoocommerceWordPress extension · Visser

CVE-2016-10922

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 1.5.7 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.7 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 · moderate confidence

The woocommerce-store-toolkit plugin before version 1.5.7 for WordPress contains a privilege escalation vulnerability allowing attackers to gain elevated privileges, likely through improper capability checks on AJAX actions or admin functionality, enabling users with low-level permissions to escalate to administrator access.

MitigationUpdate the woocommerce-store-toolkit plugin to version 1.5.7 or later to remediate the privilege escalation vulnerability. If immediate update is not possible, consider disabling the plugin or implementing additional access controls at the web application firewall level.

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.7

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 plugin installation directory
    Navigate to your WordPress wp-content/plugins/ directory and look for a folder named 'woocommerce-store-toolkit', 'visser-store-toolkit-for-woocommerce', or similar. Alternatively, log into WordPress admin and go to Plugins > Installed Plugins to list all plugins.
    Affected if the plugin folder or listing exists in your WordPress installation
  2. Identify the installed plugin version
    If using WordPress admin, find the plugin in the Installed Plugins list and read the version number displayed beneath the plugin name. If accessing files directly, open the main plugin PHP file (usually named something like 'woocommerce-store-toolkit.php') and look for the 'Version' header in the plugin comment block at the top of the file.
    Affected if the version displayed is less than 1.5.7 or the Version header cannot be read or is missing
  3. Verify the plugin is active
    In WordPress admin under Plugins > Installed Plugins, check if the plugin has an 'Active' status under the plugin name. Alternatively, query the wp_options table in your WordPress database for option_name containing 'active_plugins'.
    Affected if the plugin shows as Active in the WordPress plugin management interface

You are affected if the woocommerce-store-toolkit plugin is installed, enabled, and running a version numbered lower than 1.5.7.

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

Update the woocommerce-store-toolkit plugin to version 1.5.7 or later to remediate the privilege escalation vulnerability. If immediate update is not possible, consider disabling the plugin or implementing additional access controls at the web application firewall level.

Recommended fix High confidence

1.5.7

  1. Backup your WordPress site (both database and files)
  2. Log in to WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate 'Store Toolkit for WooCommerce' in the plugin list
  5. Click 'Update Now' if an update to version 1.5.7 or higher is available, or manually upload version 1.5.7
  6. Verify the update was successful by checking the installed version number

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

Fix this in Store Toolkit For Woocommerce Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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