dbcve.org
Consulting Elementor WidgetsWordPress extension · Stylemixthemes

CVE-2024-37089

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-24
Fix available
A fix is available. Upgrade to 1.3.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
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 · moderate confidence

A path traversal vulnerability in StylemixThemes Consulting Elementor Widgets plugin (versions up to 1.3.0) allows unauthenticated attackers to perform PHP Local File Inclusion (LFI) by manipulating file path parameters. Combined with the critical CVSS score of 9.8, this likely enables remote code execution through the inclusion of malicious or existing PHP files on the server.

MitigationUpdate Consulting Elementor Widgets to the latest patched version immediately. If no patched version is available, disable or remove the plugin until a fix is released.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Consulting Elementor Widgets plugin is installed
    Check your WordPress plugins directory for the consulting-elementor-widgets folder, or list installed plugins via wp-cli: wp plugin list --name='consulting-elementor-widgets'
    Affected if The plugin folder or listing exists in your WordPress installation
  2. Check the installed plugin version
    Read the main plugin file (usually consulting-elementor-widgets/main.php or consulting-elementor-widgets/plugin.php) and locate the 'Version' header in the plugin comments, or use: wp plugin get consulting-elementor-widgets --field=version
    Affected if The reported version is less than 1.3.1 (for example: 1.3.0, 1.2.x, 1.1.0, etc.)
  3. Confirm the plugin is active on the site
    Check the WordPress database wp_options table for the option 'active_plugins', or use: wp plugin is-active consulting-elementor-widgets
    Affected if The plugin appears in the active_plugins array or wp-cli returns that it is active
  4. Inspect for suspicious incoming requests
    Review web server access logs (Apache, Nginx) for patterns like '../' or '..%2f' in query parameters targeting the plugin's AJAX endpoint or widget files, typically around /wp-admin/admin-ajax.php with action parameters related to the plugin
    Affected if Unauthenticated requests contain path traversal sequences (../, ..%2f, %2e%2e/) pointing to PHP files outside the expected plugin directory

Your environment is affected if the Consulting Elementor Widgets plugin is installed with a version below 1.3.1 and the plugin is active, exposing the vulnerable file path parameter handling to unauthenticated attackers.

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 patched version immediately. If no patched version is available, disable or remove the plugin until a fix is released.

Recommended fix High confidence

1.3.1

  1. 1. Log in to the WordPress admin dashboard where the Consulting Elementor Widgets plugin/theme is installed.
  2. 2. Navigate to Plugins or Themes section, depending on how Consulting Elementor Widgets is installed.
  3. 3. Locate Consulting Elementor Widgets in the list of installed plugins/themes.
  4. 4. Check the current version to confirm it is below 1.3.1 (vulnerable versions are through 1.3.0).
  5. 5. If an update is available, click Update Now or Update to upgrade to version 1.3.1.
  6. 6. If automatic updates are not available, manually download version 1.3.1 from the vendor (StylemixThemes) and upload/replace the existing installation.
  7. 7. After updating, verify the new version number displays as 1.3.1 or higher.
  8. 8. Test the Consulting Elementor Widgets functionality to ensure the update did not break expected features.

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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