dbcve.org
Consulting Elementor WidgetsWordPress extension · Stylemixthemes

CVE-2024-37091

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 Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in StylemixThemes Consulting Elementor Widgets, StylemixThemes Masterstudy Elementor Widgets allows OS Command Injection.This issue affects Consulting Elementor Widgets: from n/a through 1.3.0; Masterstudy Elementor Widgets: from n/a through 1.2.2.

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

Command injection vulnerability in StylemixThemes Consulting Elementor Widgets (versions up to 1.3.0) and Masterstudy Elementor Widgets (versions up to 1.2.2) allows remote attackers to execute arbitrary OS commands due to improper neutralization of special elements in plugin parameters.

MitigationUpdate Consulting Elementor Widgets to version 1.3.1 or later and Masterstudy Elementor Widgets to version 1.2.3 or later; if updates are unavailable, consider removing the affected plugins until a patch 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
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 if Consulting Elementor Widgets is installed
    Navigate to WordPress admin > Plugins and locate the StylemixThemes Consulting Elementor Widgets plugin, or check the plugin files for version information in the main plugin file header
    Affected if The plugin is installed and the version is below 1.3.1
  2. Check if Masterstudy Elementor Widgets is installed
    Navigate to WordPress admin > Plugins and locate the StylemixThemes Masterstudy Elementor Widgets plugin, or check the plugin files for version information in the main plugin file header
    Affected if The plugin is installed and the version is below 1.2.2 or 1.2.3 (the fix version)
  3. Verify plugin version via file inspection
    Access the WordPress filesystem and open the main plugin PHP file (typically contains plugin header with Version field) to confirm the exact installed version
    Affected if The version displayed is lower than the fixed versions (1.3.1 for Consulting, 1.2.3 for Masterstudy)

Your environment is affected if either StylemixThemes Consulting Elementor Widgets below version 1.3.1 or Masterstudy Elementor Widgets below version 1.2.3 is installed and active.

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 version 1.3.1 or later and Masterstudy Elementor Widgets to version 1.2.3 or later; if updates are unavailable, consider removing the affected plugins until a patch is released.

Recommended fix Moderate confidence

Consulting Elementor Widgets version 1.3.1; Masterstudy Elementor Widgets version 1.2.3 or later (if available)

  1. 1. Identify all WordPress sites using Consulting Elementor Widgets or Masterstudy Elementor Widgets plugins by StylemixThemes
  2. 2. For Consulting Elementor Widgets: Navigate to the WordPress admin dashboard > Plugins section
  3. 3. Check the current installed version of Consulting Elementor Widgets in the Plugins list
  4. 4. If the installed version is below 1.3.1, update the plugin to version 1.3.1 or later
  5. 5. For Masterstudy Elementor Widgets: Check if version 1.2.3 or later is available and update accordingly
  6. 6. After updating, verify the plugin version has been successfully upgraded in the Plugins section
  7. 7. Test the site functionality to ensure the update did not break any existing 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
  • 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-37091 — 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-37091 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