dbcve.org
CWE-640Weakness · CWE-640

CVE-2026-15155

HIGH · 8.8 CVSS v3.1 Published 2026-07-11
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 6 weeks old

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 Authenticated Account Takeover via Email Header Injection in all versions up to, and including, 6.6.10 This is due to insufficient server-side validation of a Login/Register widget setting used to construct outgoing email headers — the allowed-values restriction is enforced only in the client-side editor UI and not on the server, and the applied sanitization does not strip or encode CR/LF characters, allowing CRLF sequences stored in that setting to survive into raw mail headers. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject an additional Bcc header into the WordPress administrator's password-reset notification email, receive a copy of a valid administrator password-reset link, and achieve full administrator account takeover.

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

This is an email header injection vulnerability in the Essential Addons for Elementor plugin's Login/Register widget. The plugin performs client-side validation only, failing to sanitize CR/LF characters server-side, allowing authenticated Contributor+ users to inject arbitrary Bcc headers into WordPress password-reset emails by storing CRLF sequences in widget settings, enabling interception of admin password-reset links and full account takeover.

MitigationUpdate Essential Addons for Elementor to version 6.6.11 or later, which should implement server-side validation and strip CR/LF characters from email header inputs.

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 Essential Addons for Elementor is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate Essential Addons for Elementor in the list
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    Look at the version number listed next to Essential Addons for Elementor in the Plugins screen, or inspect the plugin header in /wp-content/plugins/essential-addons-for-elementor/includes/index.php
    Affected if The version is below 6.6.11 (e.g., 6.6.10, 6.5.x, etc.)
  3. Identify pages using the Login/Register widget
    In Elementor editor, search for the Login/Register widget, or query the WordPress postmeta table for _elementor_data containing 'login-register' widget type
    Affected if Any published page or post contains the Essential Addons Login/Register widget
  4. Inspect Login/Register widget email settings
    Edit each page with the Login/Register widget in Elementor, open widget settings, and check the Login/Register Form > Additional Options > Email settings for any unexpected or suspicious values in header fields
    Affected if The widget settings contain unexpected Bcc, Cc, or From headers, or contain line break characters (any content you did not intentionally configure)
  5. Check for unauthorized password reset activity
    Review WordPress email logs or server mail logs for password reset emails sent to addresses you do not recognize, especially Bcc recipients
    Affected if Password reset emails have been sent to unexpected external addresses

You are affected if Essential Addons for Elementor version below 6.6.11 is installed AND the Login/Register widget is active on your site, as this combination allows authenticated Contributor+ users to inject arbitrary email headers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Essential Addons for Elementor to version 6.6.11 or later, which should implement server-side validation and strip CR/LF characters from email header inputs.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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