dbcve.org
AvadaWordPress extension · Theme Fusion

CVE-2024-2340

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 7.11.7 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 theme for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 7.11.6 via the '/wp-content/uploads/fusion-forms/' directory. This makes it possible for unauthenticated attackers to extract sensitive data uploaded via an Avada created form with a file upload mechanism.

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 WordPress theme exposes the fusion-forms upload directory (`/wp-content/uploads/fusion-forms/`) without authentication, allowing unauthenticated attackers to access sensitive files uploaded through Avada form builder's file upload feature. This is a direct information disclosure vulnerability where form submissions containing personal data, documents, or other sensitive uploads are publicly accessible.

MitigationUpdate to Avada theme version 7.11.7 or later. Additionally, configure web server access controls (e.g., .htaccess rules or Nginx location blocks) to restrict direct access to the fusion-forms directory, requiring proper authentication or blocking public access entirely.

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.7

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Check installed Avada theme version
    Navigate to WordPress admin > Appearance > Themes to view the active theme version, or check the style.css file in the Avada theme directory for the Version header
    Affected if The installed version is below 7.11.7
  2. Verify fusion-forms upload directory exists
    Check if the directory /wp-content/uploads/fusion-forms/ exists on the web server filesystem
    Affected if The directory exists on the server
  3. Test unauthenticated access to the upload directory
    Using a web browser or curl command, navigate directly to http(s)://yourdomain.com/wp-content/uploads/fusion-forms/ without logging in
    Affected if The directory is accessible and displays a listing of files or allows file download without authentication
  4. Inspect directory protection configuration
    Check if there is an .htaccess file inside /wp-content/uploads/fusion-forms/ with Deny rules, or check Nginx/Vhost configuration for the location block restricting access
    Affected if No access controls are configured and the directory is publicly readable
  5. Review file upload feature status
    Check WordPress admin > Avada > Forms to see if any forms with file upload fields are published and active
    Affected if Active forms with file upload capabilities exist and the unprotected directory is in use

You are affected if Avada theme version is below 7.11.7 AND the /wp-content/uploads/fusion-forms/ directory is publicly accessible without authentication.

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.7 or later
Fixed in 7.11.7
Interim mitigation

Update to Avada theme version 7.11.7 or later. Additionally, configure web server access controls (e.g., .htaccess rules or Nginx location blocks) to restrict direct access to the fusion-forms directory, requiring proper authentication or blocking public access entirely.

Recommended fix High confidence

Avada 7.11.7

  1. Upgrade the Avada theme to version 7.11.7 or later by navigating to Dashboard > Appearance > Themes in WordPress and updating the Avada theme

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

Fix this in Avada Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2340 — 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-2340 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