CVE-2024-4449
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 · uneditedThe Essential Addons for Elementor – Best Elementor Templates, Widgets, Kits & WooCommerce Builders plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'Fancy Text', 'Filter Gallery', 'Sticky Video', 'Content Ticker', 'Woo Product Gallery', & 'Twitter Feed' widgets in all versions up to, and including, 5.9.19 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 confidenceStored XSS vulnerability in Essential Addons for Elementor plugin allows authenticated contributors+ to inject arbitrary JavaScript via six widget types (Fancy Text, Filter Gallery, Sticky Video, Content Ticker, Woo Product Gallery, Twitter Feed) due to missing input sanitization and output escaping on user-supplied attributes.
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< 5.9.20CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Essential Addons for Elementor is installedLog into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the file /wp-content/plugins/essential-addons-for-elementor/readme.txt for the version lineAffected if The plugin is present on the site
-
Determine the installed version numberIn WordPress admin, find the plugin in the plugins list and note the version number displayed, or run: grep -i 'Stable tag' /wp-content/plugins/essential-addons-for-elementor/readme.txtAffected if Version is lower than 5.9.20 (e.g., 5.9.19, 5.9.18, etc.)
-
Identify use of affected widgetsReview pages, posts, and templates for any instances of these six widgets: Fancy Text, Filter Gallery, Sticky Video, Content Ticker, Woo Product Gallery, Twitter Feed. In Elementor editor, these appear under the Essential Addons category.Affected if Any of the six affected widgets are in use on the site
-
Inspect saved widget content for malicious scriptsExamine the HTML source or database wp_postmeta table for saved content in pages using affected widgets, looking for <script> tags or javascript: URIs in attributes that accept user input such as link URLs, custom CSS classes, or text fieldsAffected if Unexpected script tags or javascript: handlers are found in widget content attributes
You are affected if Essential Addons for Elementor version is below 5.9.20 AND any of the six vulnerable widgets (Fancy Text, Filter Gallery, Sticky Video, Content Ticker, Woo Product Gallery, Twitter Feed) are in use on the site with contributor-authored content.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.9.20
Update plugin to version 5.9.20 or later; audit existing pages using affected widgets for injected malicious scripts and remove them.
Essential Addons For Elementor 5.9.20 or later
- Backup your WordPress site before making any changes
- Navigate to Dashboard > Plugins in WordPress admin
- Locate 'Essential Addons for Elementor' in the installed plugins list
- Click 'Update now' to install version 5.9.20 or later
- Alternatively, download the latest version from wordpress.org/plugins/essential-add-for-elementor/ and upload manually if automatic update is unavailable
- After updating, verify the plugin version shows 5.9.20 or higher under Plugins > Installed Plugins
- Test the affected widgets (Fancy Text, Filter Gallery, Sticky Video, Content Ticker, Woo Product Gallery, Twitter Feed) to confirm they function correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4449 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-4449 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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