dbcve.org
EnfoldWordPress extension · Kriesi

CVE-2024-13693

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-25
Fix available
A fix is available. Upgrade to 7.0 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 Enfold theme for WordPress is vulnerable to unauthorized access of data due to a missing capability check in avia-export-class.php in all versions up to, and including, 6.0.9. This makes it possible for unauthenticated attackers to export all avia settings which may included sensitive information such as the Mailchimp API Key, reCAPTCHA Secret Key, or Envato private token if they are set.

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 Enfold WordPress theme has a broken access control vulnerability in avia-export-class.php where a missing capability check allows unauthenticated users to access the theme settings export function. This exposes sensitive configuration data including Mailchimp API keys, reCAPTCHA secret keys, and Envato private tokens that may be stored in theme settings.

MitigationUpdate the Enfold theme to version 6.1 or later which includes the patch for this vulnerability. Until updated, consider disabling the export functionality at the web server level or monitoring access logs for repeated requests to export endpoints.

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
EnfoldWordPress extension
Affected:< 7.0

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 Enfold theme version
    Access WordPress admin dashboard, navigate to Enfold Theme Settings, and view the version number displayed, or inspect the style.css file in wp-content/themes/enfold/ and look for the Version: header
    Affected if The installed version is below 7.0 (e.g., 6.x versions)
  2. Locate the vulnerable export file
    Check if the file avia-export-class.php exists in the theme directory, typically at wp-content/themes/enfold/config-templatebuilder/avia-export-class.php or wp-content/themes/enfold/avia-export-class.php
    Affected if The file exists and is accessible within the theme directory structure
  3. Test unauthenticated export access
    Send a GET or POST request to the export endpoint (such as the URL path containing 'export' or 'avia-export') without providing any authentication credentials. Common patterns include ?action=avia_export or /wp-admin/admin-ajax.php?action=avia_export
    Affected if The server returns theme configuration data without requiring login or capability verification
  4. Inspect export output for sensitive data
    If the export endpoint is accessible, examine the returned data for sensitive strings: look for 'mailchimp' and 'api_key', 'recaptcha' and 'secret', 'envato' and 'token', or base64-encoded API credentials
    Affected if The export reveals Mailchimp API keys, reCAPTCHA secret keys, Envato tokens, or similar sensitive configuration values

A user is affected if they run Enfold theme version below 7.0 and the export endpoint at avia-export-class.php is reachable without authentication, exposing sensitive theme settings.

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

Update the Enfold theme to version 6.1 or later which includes the patch for this vulnerability. Until updated, consider disabling the export functionality at the web server level or monitoring access logs for repeated requests to export endpoints.

Recommended fix High confidence

Enfold 7.0

  1. 1. Back up your WordPress site (database and files) before performing any updates.
  2. 2. Navigate to your WordPress dashboard > Appearance > Themes.
  3. 3. Locate the Enfold theme and check for available updates.
  4. 4. Update the Enfold theme to version 7.0 or later.
  5. 5. After updating, verify that the avia-export-class.php file now includes proper capability checks.
  6. 6. Consider re-generating any API keys that may have been exposed (Mailchimp API Key, reCAPTCHA Secret Key, Envato private token).
Caveat Major version upgrades may include template changes, deprecated functions, or altered theme options - test in a staging environment before deploying to production

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

Fix this in Enfold Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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