IgnitionDeck Crowdfunding Platform <= 1.1.6 - Missing Authorization

2015-03-06 00:00
James Golovich

Strategic Overview

Status
Patched in 1.1.7
Affected Version
<= 1.1.6
CVSS
7.3High
Weakness type
CWE-287 · Improper Authentication
CVE
CVE pending
View all IgnitionDeck Crowdfunding Platform vulnerabilities

At a glance

This record tracks a high-severity Improper Authentication vulnerability in the IgnitionDeck Crowdfunding Platform WordPress plugin, affecting versions <= 1.1.6. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.7; sites on affected versions should update now. Disclosed March 2015, reported by James Golovich.

Vulnerability Overview

The IgnitionDeck Crowdfunding Platform plugin for WordPress is vulnerable to authorization bypass in versions up to, and including, 1.1.6. This is due to missing capability checks on various functions called via AJAX actions. This makes it possible for unauthenticated attackers to execute various AJAX actions including one that would grant the attacker various permissions that could be used to modify many of the plugin's settings and features.

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.

CWE-287: Improper Authentication

Reaching this weakness in IgnitionDeck Crowdfunding Platform <= 1.1.6 takes a caller who can reach the endpoint. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For IgnitionDeck Crowdfunding Platform the fix is 1.1.7: builds <= 1.1.6 are affected, anything from 1.1.7 onward is not.

Remediation

Update to version 1.1.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: IgnitionDeck Crowdfunding Platform 1.1.7 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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