Essential Addons For ElementorWordPress extension · Wpdeveloper
CVE-2021-24255
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 Lite WordPress Plugin before 4.5.4 has two widgets that are vulnerable to stored Cross-Site Scripting (XSS) by lower-privileged users such as contributors, both via a similar method.
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 · moderate confidenceThe Essential Addons for Elementor Lite WordPress plugin before version 4.5.4 contains a stored Cross-Site Scripting (XSS) vulnerability in two of its widgets. Lower-privileged users such as contributors can inject malicious JavaScript code through these widgets, which executes when viewed by higher-privileged users (administrators, editors) in the Elementor page editor.
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
< 4.5.4CVSS 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 Lite is installedLog in to WordPress admin, go to Plugins > Installed Plugins, and look for 'Essential Addons for Elementor' in the listAffected if The plugin is not found in the installed plugins list
-
Check the installed version numberIn the Plugins list, locate Essential Addons for Elementor and note the version number displayed under the plugin nameAffected if The version number is less than 4.5.4 (for example, 4.5.3, 4.5.2, etc.)
-
Determine if the affected widgets are in useReview pages, posts, or templates created with Elementor that include the 'Info Box' or 'Feature List' widgets from Essential Addons (the two widgets identified as containing the XSS flaw)Affected if Either the Info Box or Feature List widget is present in any published content or draft
A user is affected if the Essential Addons for Elementor Lite plugin is installed with a version lower than 4.5.4 and any of the vulnerable widgets (Info Box or Feature List) have been used in 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.
From vendor data4.5.4
Update Essential Addons for Elementor Lite to version 4.5.4 or later to patch the XSS vulnerability. Review recent user submissions for any malicious injected scripts.
Fix this in Essential Addons For Elementor
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24255 — 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-2021-24255 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