CVE-2014-8948

iMember360 3.8.0.12 - 3.9.001 - Cross-Site Request Forgery

2014-04-24 00:00
Everett Griffiths

Strategic Overview

Status
Patched in 3.9.001
Affected Plugin
iMember360is
Affected Version
3.8.012 – < 3.9.001
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2014-8948
View all iMember360is vulnerabilities

At a glance

CVE-2014-8948 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the iMember360is WordPress plugin, affecting versions 3.8.012 – < 3.9.001. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.9.001; sites on affected versions should update now. Disclosed April 2014, reported by Everett Griffiths.

Vulnerability Overview

Cross-site request forgery (CSRF) vulnerability in the iMember360 plugin 3.8.012 through 3.9.001 for WordPress allows remote attackers to hijack the authentication of administrators for requests that with an unspecified impact via the i4w_trace parameter. NOTE: this can be leveraged with CVE-2014-8948 to execute arbitrary commands.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in iMember360is 3.8.012 – < 3.9.001 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For iMember360is the fix is 3.9.001: builds 3.8.012 – < 3.9.001 are affected, anything from 3.9.001 onward is not.

Remediation

Update to version 3.9.001, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to iMember360is: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: iMember360is 3.9.001 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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