dbcve.org
AvadaWordPress extension · Theme Fusion

CVE-2024-1668

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-13
Fix available
A fix is available. Upgrade to 7.11.6 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Avada theme for WordPress has a sensitive information exposure vulnerability in its form entries functionality. Authenticated users with contributor-level access can view all form submissions through the form entries page, including fields that should be obfuscated such as password fields. This allows low-privilege users to access potentially sensitive data they should not have access to.

MitigationUpdate the Avada theme to version 7.11.6 or later. Additionally, review user role permissions and form submissions to confirm no unauthorized access occurred while running vulnerable versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AvadaWordPress extension
Affected:< 7.11.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Avada theme is installed
    Navigate to Appearance > Themes in the WordPress admin dashboard and confirm the Avada theme is active
    Affected if Avada theme is installed and active
  2. Check installed Avada version
    Go to Appearance > Themes and click on the Avada theme to view its details. Alternatively, check the version in the theme's style.css file or in the WordPress theme directory
    Affected if The installed version is lower than 7.11.6 (e.g., 7.11.5, 7.11.0, etc.)
  3. Confirm form entries feature is in use
    Navigate to Avada > Form Entries in the admin dashboard. Check if any forms have been created and submissions exist
    Affected if Form entries exist and the form entries page is accessible in the dashboard
  4. Review user roles with contributor access
    Go to Users > All Users in WordPress admin. Identify accounts with Contributor, Author, Editor, or Administrator roles who may have access to the Form Entries section
    Affected if Multiple users with contributor-level or higher access exist who should not have visibility into all form submissions

The environment is affected if the Avada theme version is below 7.11.6 AND form entries with potentially sensitive fields are in use AND users with contributor-level access can access the Form Entries dashboard section.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.11.6 or later
Fixed in 7.11.6
Interim mitigation

Update the Avada theme to version 7.11.6 or later. Additionally, review user role permissions and form submissions to confirm no unauthorized access occurred while running vulnerable versions.

Recommended fix High confidence

Avada 7.11.6 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. Locate the Avada theme
  4. If an update is available, click on 'Update Now' to update to the latest version
  5. Alternatively, download Avada version 7.11.6 or later from the theme vendor and upload via WordPress > Appearance > Themes > Add New > Upload Theme
  6. Verify the version after update by checking Themes > Avada > Theme Details
Caveat Review theme changelog and test in staging environment before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Avada Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1668 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1668 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data