CVE-2017-18607

Avada <= 5.1.4 - Cross-Site Request Forgery

2017-04-26 00:00
Anonymous

Strategic Overview

Status
Patched in 5.1.5
Affected Version
< 5.1.5
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2017-18607
View all Avada | Website Builder For WordPress & WooCommerce vulnerabilities

At a glance

CVE-2017-18607 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Avada WordPress theme, affecting versions < 5.1.5. 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 5.1.5; sites on affected versions should update now. Disclosed April 2017.

Vulnerability Overview

The Avada theme for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 5.1.4. This is due to missing nonce validation on the fusion_builder_importer() function. This makes it possible for unauthenticated attackers to trigger the importer and upload arbitrary files 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)

Avada < 5.1.5 carries this weakness at fusion_builder_importer(), 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 Avada the fix is 5.1.5: builds < 5.1.5 are affected, anything from 5.1.5 onward is not.

Remediation

Update to version 5.1.5, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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