dbcve.org
Ultimate Addons For ElementorWordPress extension · Brainstormforce

CVE-2024-37455

HIGH · 8.8 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 1.36.32 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 Privilege Management vulnerability in Brainstorm Force Ultimate Addons for Elementor allows Privilege Escalation.This issue affects Ultimate Addons for Elementor: from n/a through 1.36.31.

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

Improper privilege management in Ultimate Addons for Elementor permits authenticated users to elevate their privileges beyond their assigned role, potentially achieving administrator-level access. The vulnerability exists in versions up to 1.36.31 and stems from insufficient validation of user capabilities before performing privileged operations.

MitigationUpdate Ultimate Addons for Elementor to the latest version beyond 1.36.31 which should contain the privilege management fix. If no patched version is available, consider disabling the plugin until a fix is released, or implement additional access controls at the WordPress server level.

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
Ultimate Addons For ElementorWordPress extension
Affected:< 1.36.32

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 Ultimate Addons for Elementor is installed
    Check your WordPress installation plugins directory, typically at wp-content/plugins/ultimate-addons-for-elementor/, or view the installed plugins in the WordPress admin under Plugins > Installed Plugins
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for the Ultimate Addons for Elementor entry to see the version number, or read the main plugin file header at wp-content/plugins/ultimate-addons-for-elementor/ultimate-addons-for-elementor.php
    Affected if The version number is less than 1.36.32 (for example, 1.36.31, 1.36.30, etc.)
  3. Review user accounts for unauthorized administrators
    In WordPress admin, go to Users > All Users and examine the list of users with Administrator role. Look for accounts you do not recognize, accounts created recently that you did not create, or accounts with suspicious usernames
    Affected if There are administrator accounts that were not created by known administrators or that you do not recognize
  4. Check for suspicious user capability modifications
    Use WordPress user query functions or review user_meta table entries to check if any non-administrator users have had their capabilities modified to include administrative-level permissions
    Affected if Non-administrator users have administrative capabilities or elevated privileges beyond their assigned role

A user is affected if the Ultimate Addons for Elementor plugin version is below 1.36.32 and there is evidence of unauthorized privilege escalation or unexpected administrator accounts in the WordPress user database.

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

Update Ultimate Addons for Elementor to the latest version beyond 1.36.31 which should contain the privilege management fix. If no patched version is available, consider disabling the plugin until a fix is released, or implement additional access controls at the WordPress server level.

Recommended fix High confidence

1.36.32

  1. Backup your WordPress site before performing any updates
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Find 'Ultimate Addons for Elementor' in the plugin list
  4. Click 'Update now' when an update is available, or manually download and install version 1.36.32 or later
  5. After updating, verify the plugin version shows 1.36.32 or higher in the plugins list
  6. Test your Elementor pages and widgets to ensure the update did not break any functionality

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

Fix this in Ultimate Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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