dbcve.org
EnfoldWordPress extension · Kriesi

CVE-2024-37199

MEDIUM · 6.1 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 5.6.10 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Kriesi.At Enfold allows Reflected XSS.This issue affects Enfold: from n/a through 5.6.9.

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 · moderate confidence

A reflected Cross-Site Scripting (XSS) vulnerability exists in the Kriesi.At Enfold WordPress theme. The vulnerability stems from improper neutralization of user-supplied input during web page generation, allowing attackers to inject malicious scripts that execute in victims' browsers via reflected XSS.

MitigationUpgrade to Enfold version 5.7 or later where the vulnerability is patched; alternatively, implement proper output encoding and input validation on affected parameters.

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:< 5.6.10

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Confirm Enfold theme installation
    Access WordPress admin dashboard, navigate to Appearance > Themes, and verify that the Enfold theme is currently active or installed
    Affected if Enfold theme is active or installed on the WordPress site
  2. Identify Enfold theme version
    In WordPress admin, go to Enfold > Version (or check the theme header file via file system at wp-content/themes/enfold/style.css for the Version: field)
    Affected if Unable to determine the installed version number for comparison
  3. Compare against affected version range
    Compare the identified version number to the affected range: versions prior to 5.6.10 are vulnerable
    Affected if Installed version is lower than 5.6.10 (for example, 5.6.9, 5.6, 5.5.x, etc.)
  4. Identify vulnerable reflected parameter
    Review HTTP requests and responses for user-supplied input that is reflected without encoding in page output; common XSS vectors in themes include search parameters, form inputs, or URL-based parameters
    Affected if Version is below 5.6.10 AND unsanitized user input is reflected in page content without proper output encoding

The environment is affected if the Enfold theme version is below 5.6.10 and user-supplied input is reflected in web pages without encoding, allowing script injection via reflected XSS.

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

Upgrade to Enfold version 5.7 or later where the vulnerability is patched; alternatively, implement proper output encoding and input validation on affected parameters.

Recommended fix High confidence

Enfold 5.6.10

  1. Create a complete backup of the WordPress site including database and files
  2. Download Enfold theme version 5.6.10 from a trusted source (ThemeForest or official Kriesi.at website)
  3. Install the Enfold 5.6.10 theme update via WordPress Appearance > Themes admin, or upload via FTP
  4. Verify the theme version shows 5.6.10 in WordPress admin after update
  5. Clear any caching layers (site cache, CDN cache, server-side cache)
  6. Test that the application functions normally after the update
Caveat Review Enfold changelog for 5.6.10 for any child theme or functionality changes that may require adjustments

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

Fix this in Enfold Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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