dbcve.org
Essential Addons For ElementorWordPress extension · Wpdeveloper

CVE-2024-9993

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-07
Fix available
A fix is available. Upgrade to 6.1.13 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 – Best Elementor Addon, Templates, Widgets, Kits & WooCommerce Builders plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the eael_event_details_text parameter of Event Calendar Widget in all versions up to, and including, 6.1.12 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-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 Cross-Site Scripting (XSS) vulnerability in the Essential Addons for Elementor plugin's Event Calendar Widget. Authenticated attackers with contributor-level access can inject arbitrary JavaScript via the eael_event_details_text parameter due to insufficient input sanitization and output escaping, causing scripts to execute when users access affected pages.

MitigationUpdate Essential Addons for Elementor to version 6.1.13 or later which contains proper input sanitization and output escaping for the affected widget parameter.

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
Essential Addons For ElementorWordPress extension
Affected:< 6.1.13

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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
    Go to WordPress Admin > Plugins and confirm 'Essential Addons for Elementor' by Wpdeveloper is listed as an active plugin
    Affected if The plugin is installed and active
  2. Check installed plugin version
    In Plugins list, click on Essential Addons for Elementor to view the version number, or compare against the affected range (versions prior to 6.1.13)
    Affected if The installed version is below 6.1.13
  3. Identify Event Calendar Widget usage
    Navigate to Pages or Posts in WordPress Admin, edit any content, and look for the Event Calendar widget from Essential Addons in Elementor editor. Alternatively, search database for posts containing 'eael_event_calendar' meta value
    Affected if The Event Calendar widget is present in any published content
  4. Inspect the eael_event_details_text parameter
    If Event Calendar widget is in use, edit the page/post, click the widget, expand the Event Details section in the widget settings, and examine any text field values for unsanitized content
    Affected if Custom text has been entered in event details fields without proper encoding

You are affected if Essential Addons for Elementor is installed with a version below 6.1.13 AND the Event Calendar widget with custom event details text is used on any page or post.

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 6.1.13 or later
Fixed in 6.1.13
Interim mitigation

Update Essential Addons for Elementor to version 6.1.13 or later which contains proper input sanitization and output escaping for the affected widget parameter.

Recommended fix High confidence

6.1.13

  1. Backup your WordPress site before making any changes
  2. Navigate to Dashboard > Plugins in your WordPress admin panel
  3. Locate 'Essential Addons for Elementor' in the installed plugins list
  4. Update the plugin to version 6.1.13 or later if an update is available
  5. Alternatively, manually download version 6.1.13 or higher from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. Verify the update was successful by checking the installed plugin version

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

Fix this in Essential Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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