dbcve.org
Element Kit For ElementorWordPress extension · La Studioweb

CVE-2024-37479

HIGH · 8.8 CVSS v3.1 Published 2024-07-02
Fix available
A fix is available. Upgrade to 1.3.9 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Local File Inclusion vulnerability in LA-Studio LA-Studio Element Kit for Elementor via "LaStudioKit Progress Bar" widget in New Post, specifically in the "progress_type" attribute.This issue affects LA-Studio Element Kit for Elementor: from n/a through 1.3.8.1.

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

Local File Inclusion vulnerability in LA-Studio Element Kit for Elementor plugin allows remote attackers to read arbitrary files on the server via the 'progress_type' attribute in the LaStudioKit Progress Bar widget. The vulnerability stems from insufficient input validation on the progress_type parameter, which is not properly sanitized before being used in file inclusion operations.

MitigationUpdate LA-Studio Element Kit for Elementor to the latest version beyond 1.3.8.1. If patching is not immediately possible, disable the LaStudioKit Progress Bar widget until the update can be applied, as LFI vulnerabilities can expose sensitive system files and credentials.

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
Element Kit For ElementorWordPress extension
Affected:< 1.3.9

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
High
Availability
High

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

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. Identify the plugin installation
    Check your WordPress installation for the LA-Studio Element Kit for Elementor plugin in wp-content/plugins/ and note the version number from the plugin header or plugin admin page
    Affected if The plugin is installed and the version is below 1.3.9 (or if version cannot be determined but the plugin is present)
  2. Verify the vulnerable widget is in use
    Review your Elementor pages and templates for instances of the LaStudioKit Progress Bar widget. Check the widget settings panel for the 'progress_type' attribute configuration
    Affected if A Progress Bar widget from this plugin is active on any published page or template
  3. Inspect the progress_type parameter handling
    Examine the plugin files lastudio-element-kit/includes/widgets/progress-bar.php (or similar path) to see if the progress_type parameter is used in file inclusion operations without proper sanitization
    Affected if The plugin code uses the progress_type value in include/require statements without sanitization routines such as realpath() or whitelist validation
  4. Test for LFI via HTTP request
    If you have authorization, send a crafted request to a page containing the Progress Bar widget with a manipulated progress_type parameter (for example: ?progress_type=../../../../etc/passwd) to confirm the vulnerability exists in your environment
    Affected if The server returns content from files outside the intended directory

Your environment is affected if LA-Studio Element Kit for Elementor is installed with a version below 1.3.9 AND the Progress Bar widget is in use on a published page, allowing unauthenticated attackers to manipulate the progress_type parameter to read arbitrary files.

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

Update LA-Studio Element Kit for Elementor to the latest version beyond 1.3.8.1. If patching is not immediately possible, disable the LaStudioKit Progress Bar widget until the update can be applied, as LFI vulnerabilities can expose sensitive system files and credentials.

Recommended fix High confidence

1.3.9

  1. Backup your WordPress site and database before performing any updates
  2. Navigate to your WordPress admin dashboard
  3. Go to Plugins > Installed Plugins
  4. Locate 'LA-Studio Element Kit for Elementor' in the plugin list
  5. Update the plugin to version 1.3.9 or later
  6. Verify the plugin is running version 1.3.9 or higher after the update

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

Fix this in Element Kit For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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