dbcve.org
Essential Addons For ElementorWordPress extension · Wpdeveloper

CVE-2024-1276

MEDIUM · 6.4 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to 5.9.9 or later.
See remediation →
70/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 – Best Elementor Templates, Widgets, Kits & WooCommerce Builders plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Content Ticker arrow attribute in all versions up to, and including, 5.9.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access or 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

The Essential Addons for Elementor plugin versions up to 5.9.8 contains a stored XSS vulnerability in the Content Ticker widget's arrow attribute. Authenticated users with contributor-level access or higher can inject malicious JavaScript through insufficiently sanitized input, which persists in the database and executes when other users view affected pages due to missing output escaping.

MitigationUpgrade to version 5.9.9 or later which contains proper input sanitization and output escaping for the Content Ticker arrow attribute. If immediate upgrade is not possible, restrict contributor-level access until patched.

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:< 5.9.9

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. Identify Essential Addons for Elementor version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Essential Addons for Elementor'. The version number is displayed in the plugin description column. Alternatively, inspect the plugin main file header in wp-content/plugins/essential-addons-for-elementor/
    Affected if Version is 5.9.8 or lower (below 5.9.9)
  2. Locate Content Ticker widget usage
    In WordPress admin with Elementor enabled, review all pages/posts created with Elementor. Look for any pages using the Content Ticker widget. This can also be queried in the database by searching wp_postmeta for meta_key containing 'content_ticker' or 'ea-ticker'
    Affected if The Content Ticker widget is present on any published page or post
  3. Inspect Content Ticker arrow attribute in database
    Query the wp_postmeta table for meta_value containing arrow settings. Look for patterns like 'ea-ticker-arrow' or serialized data containing arrow configuration. Example SQL: SELECT * FROM wp_postmeta WHERE meta_value LIKE '%ticker%arrow%'
    Affected if Arrow attribute value contains unsanitized input such as javascript:, onload=, or script tags
  4. Verify contributor-level user access
    Check WordPress user roles at Users > All Users. Identify any users with Contributor, Author, Editor, or Administrator role who have access to edit Elementor content
    Affected if At least one user with Contributor-level access or higher exists who could have modified the Content Ticker widget settings

Environment is affected if Essential Addons for Elementor version is below 5.9.9 AND the Content Ticker widget with a crafted arrow attribute value exists in any published page or post accessible to other users.

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

Upgrade to version 5.9.9 or later which contains proper input sanitization and output escaping for the Content Ticker arrow attribute. If immediate upgrade is not possible, restrict contributor-level access until patched.

Recommended fix High confidence

Essential Addons For Elementor version 5.9.9

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Essential Addons for Elementor' in the plugin list
  4. If an update is available, click 'Update Now' to update to version 5.9.9 or later
  5. Alternatively, go to Dashboard > Updates and update the plugin from there
  6. After updating, verify the plugin version shows 5.9.9 or higher under Plugins > Installed Plugins
  7. Review any pages using the Content Ticker widget to ensure existing content is not malformed
Caveat Review custom CSS/JS or template overrides after updating, as minor version updates may include widget behavior changes

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-1276 — 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-1276 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