dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-7284

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The Easy Elements for Elementor – Addons & Website Templates plugin for WordPress is vulnerable to privilege escalation via user registration in all versions up to, and including, 1.4.4. This is due to the 'easyel_handle_register' function not restricting what user roles a user can register with. This makes it possible for unauthenticated attackers to supply the 'administrator' role during registration and gain administrator access to the site.

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 Easy Elements for Elementor plugin has a privilege escalation vulnerability in its user registration function 'easyel_handle_register'. This function does not validate or restrict the user role parameter during registration, allowing unauthenticated attackers to specify 'administrator' as their role and gain full admin access to the WordPress site.

MitigationUpdate the plugin to version 1.4.5 or later when available. Until then, disable user registration functionality if not needed, and audit existing administrator accounts for unauthorized access.

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
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 Easy Elements for Elementor is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Easy Elements for Elementor', or check the /wp-content/plugins/ directory for the easy-elements-for-elementor folder
    Affected if The plugin is present on the site
  2. Determine the installed plugin version
    In WordPress admin_plugins list, click on the plugin to view its details and note the version number, or inspect the main plugin file header in /wp-content/plugins/easy-elements-for-elementor/
    Affected if Version is at or below 1.4.4 (if known) or the version cannot be determined but the plugin is present
  3. Confirm the registration functionality is enabled
    Look for any registration-related settings in the plugin options (Easy Elements settings page) or check if the function 'easyel_handle_register' is hooked to an action like 'init' or 'wp_ajax_nopriv_easyel_register' by examining the plugin code in /wp-content/plugins/easy-elements-for-elementor/
    Affected if Registration functionality is active or the vulnerable registration handler is present in the code
  4. Inspect for unauthorized administrator accounts
    Go to WordPress Users admin panel and review all accounts with Administrator role, looking for unfamiliar accounts or ones created recently that you did not create
    Affected if There are administrator accounts you did not create or do not recognize

If the Easy Elements for Elementor plugin is installed with its registration feature enabled, the site is likely vulnerable to unauthenticated administrator account creation.

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 plugin to version 1.4.5 or later when available. Until then, disable user registration functionality if not needed, and audit existing administrator accounts for unauthorized access.

Recommended fix Moderate confidence

Latest available version of Easy Elements for Elementor for WordPress (version > 1.4.4)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find 'Easy Elements for Elementor – Addons & Website Templates'
  4. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org/plugins/easy-elements-for-elementor and upload it
  5. Verify the updated version is newer than 1.4.4
  6. Test user registration functionality to confirm the privilege escalation vulnerability is remediated

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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