dbcve.org
Master AddonsWordPress extension

CVE-2024-2139

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 2.0.5.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The Master Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Pricing Table widget in all versions up to, and including, 2.0.5.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

The Master Addons for Elementor plugin for WordPress contains a Stored Cross-Site Scripting (XSS) vulnerability in the Pricing Table widget. The flaw exists due to insufficient input sanitization and output escaping, allowing authenticated attackers with contributor-level access or higher to inject malicious JavaScript code that executes when users view the affected pages.

MitigationUpdate the Master Addons for Elementor plugin to version 2.0.6 or later. If immediate updating is not possible, restrict or disable the Pricing Table widget until the patch can be applied.

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.7

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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
    In WordPress admin, navigate to Plugins > Installed Plugins and locate 'Master Addons for Elementor' in the list. Note whether it is active.
    Affected if The plugin is installed and active
  2. Check installed plugin version
    Click on the plugin name in the plugins list to view version details, or check the plugin header in /wp-content/plugins/master-addons-for-elementor/master-addons.php
    Affected if Version is lower than 2.0.5.7
  3. Identify if Pricing Table widget is in use
    Edit pages or templates using the Elementor editor. Check if the Master Addons Pricing Table widget has been added to any published pages. Inspect page content or use a database query on wp_posts to search for 'pricing-table' or 'ma-pricing-table' shortcodes or widget markers.
    Affected if The Pricing Table widget is present on any published page or post
  4. Review user role permissions
    Navigate to WordPress Users > All Users and identify which users have Contributor, Author, Editor, or Administrator roles, as these roles can access the Elementor editor and potentially exploit the vulnerability.
    Affected if Any user with Contributor-level access or higher exists on the site

Your environment is affected if Master Addons for Elementor plugin version is below 2.0.5.7 AND the Pricing Table widget is in use on your site, allowing authenticated users to potentially inject malicious scripts.

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

Update the Master Addons for Elementor plugin to version 2.0.6 or later. If immediate updating is not possible, restrict or disable the Pricing Table widget until the patch can be applied.

Recommended fix High confidence

Master Addons for Elementor version 2.0.5.7

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Master Addons for Elementor' in the plugin list
  4. Click 'Update Now' to upgrade to version 2.0.5.7
  5. Verify the update completed successfully

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

Fix this in Master Addons Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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