dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2024-32786

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 1.3.95 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
Authentication Bypass by Spoofing vulnerability in WP Royal Royal Elementor Addons allows Functionality Bypass.This issue affects Royal Elementor Addons: from n/a through 1.3.93.

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

Authentication bypass vulnerability in the Royal Elementor Addons WordPress plugin allows attackers to spoof legitimate user sessions or authentication mechanisms, potentially gaining unauthorized administrative access to WordPress sites. The 9.8 CRITICAL severity indicates a trivial exploitability issue with no user interaction required.

MitigationUpdate Royal Elementor Addons to version 1.3.94 or later immediately. If immediate update is not feasible, disable the plugin or implement additional access controls at the web 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
Royal Elementor AddonsWordPress extension
Affected:< 1.3.95

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 Royal Elementor Addons is installed
    Check your WordPress site's plugin directory at wp-content/plugins/ for a folder named 'royal-elementor-addons' or look for the plugin in the WordPress admin under Plugins > Installed Plugins.
    Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress plugins list.
  2. Determine installed plugin version
    Open the main plugin file (typically wp-content/plugins/royal-elementor-addons/royal-elementor-addons.php) and locate the version comment at the top of the file, or check the version field in the WordPress admin plugin list.
    Affected if The displayed version number is less than 1.3.95.
  3. Confirm vulnerability is exploitable
    This authentication bypass vulnerability is inherent to the plugin versions below 1.3.95 and requires no specific configuration to be exploitable - it affects the plugin's authentication handling itself.
    Affected if The plugin version is below 1.3.95 regardless of any specific settings or configurations.
  4. Check for signs of compromise
    Review your WordPress admin user list under Users > All Users for any unfamiliar administrator accounts. Examine server access logs for requests to /wp-admin/admin-ajax.php with unusual parameters or patterns associated with this plugin.
    Affected if Unknown admin accounts exist in WordPress or log entries show suspicious activity targeting the Royal Elementor Addons plugin endpoints.

You are affected if Royal Elementor Addons plugin is installed and its version is below 1.3.95.

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

Update Royal Elementor Addons to version 1.3.94 or later immediately. If immediate update is not feasible, disable the plugin or implement additional access controls at the web server level.

Recommended fix High confidence

Royal Elementor Addons version 1.3.95

  1. Backup your WordPress site before making any changes
  2. Update Royal Elementor Addons plugin to version 1.3.95 or later
  3. Verify the update was successfully applied by checking the plugin version

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

Fix this in Royal Elementor Addons Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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