dbcve.org
Master AddonsWordPress extension

CVE-2024-35660

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 2.0.5.6 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
Missing Authorization vulnerability in Jewel Theme Master Addons for Elementor.This issue affects Master Addons for Elementor: from n/a through 2.0.5.4.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 · moderate confidence

Missing authorization vulnerability in Master Addons for Elementor plugin allows unauthenticated attackers to access sensitive functionality or perform privileged actions. The critical CVSS score (9.8) indicates this is exploitable over the network without authentication and likely provides full compromise of affected functionality.

MitigationUpdate Master Addons for Elementor to the latest version immediately. Given the critical severity and potential for unauthenticated exploitation, also conduct a security audit of the WordPress site for signs of compromise.

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
Master AddonsWordPress extension
Affected:< 2.0.5.6

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 Master Addons plugin is installed
    Check the WordPress plugin directory or wp-admin plugins page for 'Master Addons' or 'Master Addons for Elementor' in the list of installed plugins
    Affected if The plugin appears in the installed plugins list and is active
  2. Check installed plugin version
    Access the plugins page in wp-admin, locate Master Addons, and view the version number displayed beneath the plugin name
    Affected if The displayed version is below 2.0.5.6 (for example, 2.0.5.5, 2.0.4, 1.0.x, etc.)
  3. Inspect plugin file header for version
    Locate the main plugin file (usually master-addons/master-addons.php) via FTP or file manager, open it, and read the Version field in the plugin header comment
    Affected if The Version header shows a number less than 2.0.5.6
  4. Test for unauthenticated AJAX access
    Use a tool like curl or Burp to send a POST request to wp-admin/admin-ajax.php with a non-existent action (such as action=master_addons_test) without providing any authentication cookies or nonce tokens
    Affected if The server returns a 200 OK response with a valid JSON structure instead of a 400 error or a response requiring authentication (the plugin processes the request despite lack of authorization)

If Master Addons for Elementor is installed and the version is below 2.0.5.6, the environment is affected by this unauthenticated authorization bypass 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 2.0.5.6 or later
Fixed in 2.0.5.6
Interim mitigation

Update Master Addons for Elementor to the latest version immediately. Given the critical severity and potential for unauthenticated exploitation, also conduct a security audit of the WordPress site for signs of compromise.

Recommended fix High confidence

2.0.5.6

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate Master Addons for Elementor in the plugin list.
  4. 4. If an update is available, click 'Update Now' to update to the latest version.
  5. 5. Alternatively, you can download version 2.0.5.6 from the official WordPress plugin repository or the vendor's website.
  6. 6. After updating, verify the plugin is running version 2.0.5.6 or later.
  7. 7. Test critical functionality on your site to ensure the update didn't break existing features.

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

Fix this in Master Addons Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
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,912.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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