Nextend Facebook Connect <= 1.5.8 - Cross-Site Request Forgery

2016-03-15 00:00
Anonymous

Strategic Overview

Status
Patched in 1.5.9
Affected Version
<= 1.5.8
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all Nextend Social Login and Register vulnerabilities

At a glance

This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Nextend Social Login and Register WordPress plugin, affecting versions <= 1.5.8. 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 1.5.9; sites on affected versions should update now. Disclosed March 2016.

Vulnerability Overview

The Nextend Facebook Connect plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.5.8. This is due to missing nonce validation on the store_settings() function. This makes it possible for unauthenticated attackers to update the plugins settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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)

Nextend Social Login and Register <= 1.5.8 carries this weakness at store_settings(), and reaching it 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 Nextend Social Login and Register the fix is 1.5.9: builds <= 1.5.8 are affected, anything from 1.5.9 onward is not.

Remediation

Update to version 1.5.9, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Nextend Social Login and Register: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Nextend Social Login and Register 1.5.9 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