dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-5193

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 Essential Addons for Elementor – Popular Elementor Templates & Widgets plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 6.5.13. This is due to insufficient role validation in the 'register_user' function, which only blocks the 'administrator' role. This makes it possible for authenticated attackers, with author level access and above, to create new user accounts with elevated privileges such as editor.

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 Essential Addons for Elementor plugin for WordPress contains a privilege escalation vulnerability in versions up to 6.5.13. The 'register_user' function only blocks creation of administrator accounts but fails to validate that lower-privileged users (author level) cannot create accounts with higher privileges (editor). This allows authenticated attackers with author-level access to create new user accounts with elevated editor privileges.

MitigationUpdate the Essential Addons for Elementor plugin to the latest version beyond 6.5.13, which should contain proper role validation that restricts user creation to only allow roles at or below the requester's privilege level.

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Essential Addons for Elementor is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Essential Addons for Elementor'. Note the installed version number displayed below the plugin name.
    Affected if The plugin is installed and the version is 6.5.13 or lower.
  2. Confirm the plugin version is within affected range
    Compare the installed version number to 6.5.13. The vulnerability exists in versions up to and including 6.5.13.
    Affected if The installed version is 6.5.13 or any earlier version.
  3. Identify users with elevated roles created by lower-privilege accounts
    In WordPress admin, go to Users > All Users. Review the list for user accounts with Editor or higher roles that were created by accounts who had Author-level privileges. Check the 'Created By' column if available, or examine user registration timestamps and correlate with activity logs.
    Affected if There exist Editor-level accounts that were created by users who only had Author-level permissions.
  4. Audit recent user registrations for privilege escalation patterns
    Access WordPress database or use a user audit plugin to query for user registrations where the new user role is higher than the role of the creating user. Look for Author-level accounts that created Editor or Administrator accounts.
    Affected if Logs or audit data show Author-level users creating accounts with Editor or Administrator roles.

You are affected if Essential Addons for Elementor version 6.5.13 or earlier is installed AND evidence exists of lower-privilege users creating higher-privilege accounts.

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 Essential Addons for Elementor plugin to the latest version beyond 6.5.13, which should contain proper role validation that restricts user creation to only allow roles at or below the requester's privilege level.

Recommended fix High confidence

Essential Addons for Elementor version 6.5.14 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Essential Addons for Elementor' in the plugin list
  4. Check the current version number displayed under the plugin name
  5. If the installed version is 6.5.13 or lower, click 'Update Now' to install the latest available version
  6. Alternatively, navigate to Dashboard > Updates and click 'Update Now' for the Essential Addons for Elementor plugin
  7. After updating, verify the new version number in the plugins list
  8. Consider reviewing user accounts to confirm no unauthorized elevated accounts were created

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

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

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