CVE-2022-1386

Fusion Builder <= 3.6.1 & Avada <= 7.6.1 - Unauthenticated Server-Side Request Forgery

2022-04-19 00:00
Calum Elrick

Strategic Overview

Status
Patched in 7.6.2
Affected Version
< 7.6.2
CVSS
8.3High
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2022-1386
View all Avada | Website Builder For WordPress & WooCommerce vulnerabilities

At a glance

CVE-2022-1386 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Avada WordPress theme, affecting versions < 7.6.2. It carries a CVSS score of 8.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 7.6.2; sites on affected versions should update now. Disclosed April 2022, reported by Calum Elrick.

Vulnerability Overview

The Fusion Builder plugin for WordPress, an Avada theme core plugin, is vulnerable to Server-Side Request Forgery in versions up to 3.6.2 along with the Avada theme in versions up to 7.6.2. This is due to insufficient validation in one of its form parameters. This makes it possible for unauthenticated attackers to interact with internal network hosts via specially crafted requests and can lead to sensitive information disclosure on certain configurations such as AWS.

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-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in Avada < 7.6.2 takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Avada the fix is 7.6.2: builds < 7.6.2 are affected, anything from 7.6.2 onward is not.

Remediation

Update to version 7.6.2, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Avada 7.6.2 closes this, and updating the theme is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

Related records

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