LayerSlider <= 6.2.0 - Cross-Site Request Forgery to Stored Cross-Site Scripting

2017-03-28 00:00
0x21

Strategic Overview

Status
Patched in 6.2.1
Affected Plugin
LayerSlider
Affected Version
< 6.2.1
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all LayerSlider vulnerabilities

At a glance

This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the LayerSlider WordPress plugin, affecting versions < 6.2.1. 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 6.2.1; sites on affected versions should update now. Disclosed March 2017, reported by 0x21.

Vulnerability Overview

The LayerSlider plugin for WordPress is vulnerable to Cross-Site Request forgery in versions up to, and including 6.2.0, due missing nonce validation on an unspecified function that makes it possible for attackers to trick site administrators into performing unwanted 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. 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 LayerSlider < 6.2.1 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 LayerSlider the fix is 6.2.1: builds < 6.2.1 are affected, anything from 6.2.1 onward is not.

Remediation

Update to version 6.2.1, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/11aaec16-930d-44f6-abe5-4f7fdc32f252

Related records

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