Store Toolkit for WooCommerce <= 1.5.6 - Missing Authorization
Strategic Overview
- Status
- Patched in 1.5.7
- Affected Version
<= 1.5.6- CVSS
- 8.8High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2016-10922
At a glance
CVE-2016-10922 is a high-severity Missing Authorization vulnerability in the Store Toolkit WordPress plugin, affecting versions <= 1.5.6. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.5.7; sites on affected versions should update now. Disclosed February 2016, reported by James Golovich.
Vulnerability Overview
The Store Toolkit for WooCommerce plugin for WordPress is vulnerable to missing authorization checks on the woo_st_admin_init() function in versions up to, and including, 1.5.6. This makes it possible for unauthenticated attackers to gain access to restricted administrative actions and delete several different types of site content.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
Store Toolkit <= 1.5.6 carries this weakness at woo_st_admin_init(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Store Toolkit the fix is 1.5.7: builds <= 1.5.6 are affected, anything from 1.5.7 onward is not.
Remediation
Update to version 1.5.7, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Store Toolkit 1.5.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Store Toolkit – WooCommerce Extensions, Quick Enhancements & Handy Tools
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C