dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-6459

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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 Stored Cross-Site Scripting via the Event Calendar widget in all versions up to, and including, 6.6.2 due to insufficient input sanitization and output escaping on event titles sourced from The Events Calendar. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

Stored XSS vulnerability in Essential Addons for Elementor's Event Calendar widget. The plugin fails to properly sanitize event titles sourced from The Events Calendar plugin and does not escape output, allowing authenticated attackers with Author-level or higher permissions to inject malicious JavaScript that executes in users' browsers when viewing pages containing affected calendar widgets.

MitigationUpdate Essential Addons for Elementor to version 6.6.3 or later to receive the patch for this vulnerability. Audit existing pages using the Event Calendar widget for any existing malicious injections.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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 locate 'Essential Addons for Elementor' or check the plugin files for version information in the main plugin file header
    Affected if Plugin is not installed or not found
  2. Determine the installed version of Essential Addons for Elementor
    Check the plugin version number in the WordPress plugins list or read the version defined in the main plugin file (typically essential-addons-elementor.php)
    Affected if Version is below 6.6.3 (the fixed version)
  3. Confirm The Events Calendar plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and verify 'The Events Calendar' plugin is present and active
    Affected if The Events Calendar is not installed - the specific XSS vector via event title sanitization does not apply
  4. Identify pages using the Event Calendar widget
    Check pages, posts, or templates where the Event Calendar widget from Essential Addons for Elementor has been added to a Elementor layout
    Affected if Event Calendar widget is present on any published pages - this is where the XSS would execute

The environment is affected if Essential Addons for Elementor version is below 6.6.3, The Events Calendar plugin is installed, and any page contains the Event Calendar widget rendering event titles from The Events Calendar.

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 Essential Addons for Elementor to version 6.6.3 or later to receive the patch for this vulnerability. Audit existing pages using the Event Calendar widget for any existing malicious injections.

Recommended fix Moderate confidence

Version 6.6.3 or later of Essential Addons for Elementor

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Essential Addons for Elementor' in the plugin list
  4. Check if the currently installed version is 6.6.2 or earlier
  5. If vulnerable, click 'Update Now' to update to the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/essential-addons-for-elementor/ and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version number reflects the patched release
Caveat Review plugin settings after upgrade as minor interface changes may occur; test the Event Calendar widget functionality

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get help mitigating

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