Jigoshop – Store Toolkit <= 1.3.8 - Missing Authorization Checks
Strategic Overview
- Status
- Patched in 1.3.9
- Affected Plugin
- Jigoshop – Store Toolkit
- Affected Version
<= 1.3.8- CVSS
- 9.8Critical
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a critical-severity Missing Authorization vulnerability in the Jigoshop WordPress plugin, affecting versions <= 1.3.8. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.3.9; sites on affected versions should update now. Disclosed February 2016, reported by James Golovich.
Vulnerability Overview
The Jigoshop – Store Toolkit plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the 'jigo_st_admin_init' function in versions up to, and including 1.3.8. This makes it possible for unauthenticated attackers to gain access to restricted actions like deleting inactive user accounts, unlinking downloads, and more.
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 privileges on the target site, 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
Jigoshop <= 1.3.8 carries this weakness at jigo_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 Jigoshop the fix is 1.3.9: builds <= 1.3.8 are affected, anything from 1.3.9 onward is not.
Remediation
Update to version 1.3.9, 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: Jigoshop 1.3.9 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Jigoshop – Store Toolkit
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C