Elementor Addon ElementsWordPress extension · Webtechstreet
CVE-2021-24259
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 “Elementor Addon Elements” WordPress Plugin before 1.11.2 has several widgets that are vulnerable to stored Cross-Site Scripting (XSS) by lower-privileged users such as contributors, all 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 · high confidenceThe 'Elementor Addon Elements' WordPress plugin before version 1.11.2 contains multiple widgets that fail to properly sanitize user input, allowing stored Cross-Site Scripting (XSS) attacks. Contributors (low-privilege users) can inject malicious JavaScript through these widgets, which executes when higher-privileged users (editors, admins) view the affected pages in the Elementor 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
Elementor Addon ElementsWordPress extension
< 1.11.2CVSS 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 plugin installation and versionNavigate to WordPress Admin > Plugins and locate 'Elementor Addon Elements' by Webtechstreet, or use WP-CLI: wp plugin list --name='elementor-addon-elements'Affected if The plugin is installed and the version shown is below 1.11.2 (e.g., 1.11.1, 1.10, etc.)
-
Confirm plugin is activeCheck the 'Status' column in the Plugins page or run: wp plugin is-active elementor-addon-elementsAffected if The plugin is active on the site
-
Identify low-privilege user rolesGo to WordPress Admin > Users and review user accounts, or run: wp user list --role=contributorAffected if Any user accounts with Contributor role (or custom roles with similar low-level edit capabilities) exist on the site
-
Check for Elementor editor usageReview pages/posts created with Elementor by checking for 'elementor' in post meta, or manually inspect recently edited content in the Elementor editor interfaceAffected if Pages or posts have been edited using the Elementor page builder, as this is required for the malicious script to execute in the editor view
You are affected if the Elementor Addon Elements plugin version is below 1.11.2, the plugin is active, and your site has either Contributor-level users or any low-privilege users who can create/edit content viewed by higher-privileged users in the Elementor editor.
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 data1.11.2
Update the plugin to version 1.11.2 or later which includes proper input sanitization for all affected widgets. If immediate patching is not feasible, consider limiting or reviewing contributor-level access until the update can be applied.
Fix this in Elementor Addon Elements
Scoped from the published advisory
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24259 — 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-24259 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