CVE-2024-1668

Avada <= 7.11.5 - Authenticated(Contributor+) Sensitive Information Exposure via Form Entries

2024-03-01 00:00
Muhammad Zeeshan (Xib3rR4dAr)

Strategic Overview

Status
Patched in 7.11.6
Affected Theme
Avada | Website Builder For WordPress & WooCommerce
Affected Version
<= 7.11.5
CVSS
6.5Medium
Weakness type
CWE-284 · Improper Access Control
CVE
CVE-2024-1668
View all Avada | Website Builder For WordPress & WooCommerce vulnerabilities

At a glance

CVE-2024-1668 is a medium-severity Improper Access Control vulnerability in the Avada WordPress theme, affecting versions <= 7.11.5. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 7.11.6; sites on affected versions should update now. Disclosed March 2024, reported by Muhammad Zeeshan (Xib3rR4dAr).

Vulnerability Overview

The Avada | Website Builder For WordPress & WooCommerce theme for WordPress is vulnerable to Sensitive Information Exposure in versions up to and including 7.11.5 via the form entries page. This makes it possible for authenticated attackers, with contributor access and above, to view the contents of all form submissions, including fields that are obfuscated (such as the contact form's "password" field).

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 interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-284: Improper Access Control

Avada <= 7.11.5 carries this weakness at password, and reaching it takes an account at Contributor level or above. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.

Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For Avada the fix is 7.11.6: builds <= 7.11.5 are affected, anything from 7.11.6 onward is not.

Remediation

Update to version 7.11.6, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Avada 7.11.6 closes this, and updating the theme is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-1668https://www.wordfence.com/threat-intel/vulnerabilities/id/cd224169-ae51-4af8-b6de-706ed580ff8dhttps://nvd.nist.gov/vuln/detail/CVE-2024-1668

Related records

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