dbcve.org
Consulting Elementor WidgetsWordPress extension · Stylemixthemes

CVE-2024-37090

HIGH · 8.8 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to after 1.3.0 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 an SQL Command ('SQL Injection') vulnerability in StylemixThemes Masterstudy Elementor Widgets, StylemixThemes Consulting Elementor Widgets.This issue affects Masterstudy Elementor Widgets: from n/a through 1.2.2; 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

SQL injection vulnerability in StylemixThemes Masterstudy and Consulting Elementor Widgets allows attackers to inject malicious SQL commands via unsanitized user input in WordPress Elementor widget parameters. The vulnerability exists in versions through 1.2.2 and 1.3.0 respectively, requiring no authentication for exploitation.

MitigationUpdate to the latest patched version of Masterstudy and Consulting Elementor Widgets. If no patch is available, implement parameterized queries and proper input validation on all database interactions, or deploy a WAF rule to block SQL injection patterns as a temporary measure.

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.0
Masterstudy Elementor WidgetsWordPress extension
Affected:<= 1.2.2

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. Locate installed StylemixThemes plugins
    Check your WordPress installation's wp-content/plugins directory or access the Plugins admin page to list installed plugins. Identify if 'Masterstudy Elementor Widgets' and/or 'Consulting Elementor Widgets' by StylemixThemes are present.
    Affected if Either plugin is installed on the site
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins. Find the Masterstudy or Consulting Elementor Widgets plugin and view its version number in the plugin details. Alternatively, check the main plugin PHP file for the 'Version' header comment.
    Affected if The installed version is 1.2.2 or lower for Masterstudy, or 1.3.0 or lower for Consulting
  3. Verify Elementor widget usage
    Check if the vulnerable widgets are actively used on the site. In Elementor editor, look for Masterstudy or Consulting widgets added to pages. The SQL injection occurs through widget parameters, so active usage of these widgets is required for exploitation.
    Affected if The vulnerable Elementor widgets from these plugins are in use on any published page or post
  4. Review database for indicators of compromise
    Examine your WordPress database for suspicious SQL entries, unexpected records in wp_posts or wp_options, or unauthorized admin users that may have been created via the SQL injection. Check database logs if available for unusual SQL queries.
    Affected if Unexpected database changes, new admin accounts, or suspicious queries are found in logs or database tables

You are affected if either the Masterstudy Elementor Widgets plugin version 1.2.2 or lower or the Consulting Elementor Widgets plugin version 1.3.0 or lower is installed and the corresponding widgets are actively used on the site.

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.

From vendor data
Upgrade available Upgrade to a release after 1.3.0
Interim mitigation

Update to the latest patched version of Masterstudy and Consulting Elementor Widgets. If no patch is available, implement parameterized queries and proper input validation on all database interactions, or deploy a WAF rule to block SQL injection patterns as a temporary measure.

Fix this in Consulting Elementor Widgets 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-37090 — 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-37090 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