dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-3132

HIGH · 8.8 CVSS v3.1 Published 2026-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The Master Addons for Elementor Premium plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 2.1.3 via the 'JLTMA_Widget_Admin::render_preview'. This is due to missing capability check. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute code on the server.

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 Premium plugin for WordPress is vulnerable to Remote Code Execution in versions up to 2.1.3. The vulnerability exists in the JLTMA_Widget_Admin::render_preview method which lacks proper capability validation, allowing any authenticated user with Subscriber-level access (the lowest WordPress role) to execute arbitrary code on the server.

MitigationUpdate the Master Addons for Elementor Premium plugin to version 2.1.4 or later. Until the patch is applied, disable the affected plugin or implement temporary access controls at the web server level to restrict access to authenticated users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Verify Master Addons for Elementor Premium is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the plugin directory (wp-content/plugins/master-addons-for-elementor) for the main plugin file containing the version number
    Affected if The plugin is found installed on the WordPress site
  2. Determine the installed plugin version
    In WordPress admin, view the plugin details to see the version number, or open the main plugin PHP file (typically plugin-name.php) and locate the Version header in the plugin comment block
    Affected if The version is 2.1.3 or any version prior to 2.1.4 (e.g., 2.1.0, 2.0.5, 1.0.0)
  3. Confirm the presence of authenticated user accounts
    In WordPress admin, navigate to Users > All Users and review the list of registered users, noting their assigned roles
    Affected if Any user account exists with Subscriber role or any authenticated-level access (roles include Subscriber, Contributor, Author, Editor, or Administrator)
  4. Inspect the vulnerable method in plugin code
    Locate the file containing JLTMA_Widget_Admin class (typically in includes/classes or similar directory within the plugin) and examine the render_preview method for missing capability checks (look for missing current_user_can or similar authorization calls before code execution)
    Affected if The render_preview method exists and lacks proper capability validation (no current_user_can check before executing preview functionality)
  5. Verify the site allows user registration
    In WordPress admin, go to Settings > General and check if Membership option "Anyone can register" is enabled, and note the default New User Role setting
    Affected if User registration is enabled, allowing potential attackers to create low-privilege accounts
  6. Confirm the REST API or AJAX endpoints are accessible to unauthenticated users
    Review the plugin endpoints registered via wp_ajax or wp_ajax_nopriv hooks, or test accessing the vulnerable render_preview functionality with a freshly created Subscriber-level account
    Affected if The vulnerable endpoint responds to requests from authenticated users with Subscriber role without additional authorization

A site is affected if Master Addons for Elementor Premium version 2.1.3 or earlier is installed and the site has any user accounts (including Subscriber role) that can access the vulnerable render_preview method lacking capability validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Master Addons for Elementor Premium plugin to version 2.1.4 or later. Until the patch is applied, disable the affected plugin or implement temporary access controls at the web server level to restrict access to authenticated users only.

Recommended fix Moderate confidence

Master Addons for Elementor Premium version 2.1.4 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Master Addons for Elementor Premium' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is running version 2.1.4 or later
  7. 7. Test that Elementor page builder functionality continues to work properly

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

Have this fixed 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 help mitigating

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-2026-3132 — 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-2026-3132 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