WP e-Commerce – Store Exporter <= 1.6.6 - Missing Authorization

2016-02-15 00:00
James Golovich

Strategic Overview

Status
Patched in 1.6.7
Affected Version
<= 1.6.6
CVSS
9.8Critical
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE pending
View all WP e-Commerce – Store Exporter vulnerabilities

At a glance

This record tracks a critical-severity Improper Privilege Management vulnerability in the WP e-Commerce WordPress plugin, affecting versions <= 1.6.6. 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.6.7; sites on affected versions should update now. Disclosed February 2016, reported by James Golovich.

Vulnerability Overview

The WP e-Commerce – Store Exporter plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the wpsc_get_action() function in versions up to, and including 1.6.6. This makes it possible for unauthenticated attackers to gain access to restricted actions that allow them to update the plugin settings and dismiss notices among many other actions.

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-269: Improper Privilege Management

WP e-Commerce <= 1.6.6 carries this weakness at wpsc_get_action(), and reaching it takes a caller who can reach the endpoint. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For WP e-Commerce the fix is 1.6.7: builds <= 1.6.6 are affected, anything from 1.6.7 onward is not.

Remediation

Update to version 1.6.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: WP e-Commerce 1.6.7 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C