dbcve.org
Consulting Elementor WidgetsWordPress extension · Stylemixthemes

CVE-2024-37092

HIGH · 8.8 CVSS v3.1 Published 2024-06-24
Fix available
A fix is available. Upgrade to 1.3.1 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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in StylemixThemes Consulting Elementor Widgets allows PHP Local File Inclusion.This issue affects Consulting Elementor Widgets: from n/a through 1.3.0.

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

A path traversal vulnerability in StylemixThemes Consulting Elementor Widgets (versions through 1.3.0) allows attackers to use directory traversal sequences (e.g., '../') to access files outside the intended restricted directory. Combined with the PHP Local File Inclusion (LFI) capability, this can be exploited to read sensitive files and potentially achieve remote code execution by including malicious PHP files.

MitigationUpdate Consulting Elementor Widgets to the latest version to obtain the patched code that properly validates and sanitizes file paths, preventing unauthorized directory traversal and file inclusion.

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
Consulting Elementor WidgetsWordPress extension
Affected:< 1.3.1

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. Check installed plugin version
    Locate the Consulting Elementor Widgets plugin folder in wp-content/plugins (commonly named 'consulting-elementor-widgets' or similar). Open the main plugin PHP file and look for the 'Version:' header in the plugin comments, or check the readme.txt file for the version field.
    Affected if The version listed is lower than 1.3.1 (for example, 1.3.0, 1.2.x, or any version through 1.3.0).
  2. Identify the vulnerable widget file
    Examine the plugin directory for PHP files that handle file operations, particularly files containing 'include', 'require', or file path parameters. Look in folders named 'widgets', 'elementor', or 'includes'. Search for code that uses dynamic file inclusion with user-controlled input.
    Affected if The plugin contains PHP files that dynamically include files based on request parameters without proper sanitization of '../' sequences.
  3. Check for publicly accessible widget endpoints
    Test if the vulnerable widget is exposed by accessing elementor-ajax endpoints or direct widget URLs on the site. Common paths include /wp-admin/admin-ajax.php?action=consulting_elementor_widget or similar AJAX handlers that invoke the widget.
    Affected if The Consulting Elementor Widget functionality is active and accessible without authentication, allowing potential path traversal input.
  4. Review access logs for exploitation attempts
    Search web server access logs (Apache, Nginx) for requests containing '../', '..%2F', or file inclusion patterns targeting the Consulting plugin (for example, patterns like 'action=some_widget&file=../').
    Affected if Log entries show directory traversal attempts or suspicious file inclusion queries related to the Consulting Elementor Widgets plugin.

If the Consulting Elementor Widgets plugin version is below 1.3.1 and the widget functionality is publicly accessible, the environment is affected by this path traversal vulnerability.

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

Update Consulting Elementor Widgets to the latest version to obtain the patched code that properly validates and sanitizes file paths, preventing unauthorized directory traversal and file inclusion.

Recommended fix Moderate confidence

1.3.1

  1. 1. Backup your WordPress site and database before performing any updates.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the Consulting Elementor Widgets plugin by StylemixThemes.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.3.1 or later.
  5. 5. After updating, verify the plugin is running version 1.3.1 or higher in the plugins list.
  6. 6. Test the consulting-related pages and widgets to ensure functionality remains intact.

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

Fix this in Consulting Elementor Widgets Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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