CVE-2021-24266
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 “The Plus Addons for Elementor Page Builder Lite” WordPress Plugin before 2.0.6 has four 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 Plus Addons for Elementor Page Builder Lite WordPress plugin before version 2.0.6 contains four widgets affected by stored Cross-Site Scripting (XSS). The vulnerability allows lower-privileged users such as contributors to inject malicious scripts through these widgets, likely due to insufficient input sanitization and missing capability checks on the widget endpoints.
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< 2.0.6CVSS 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 versionLocate the Plus Addons for Elementor plugin in WordPress admin under Plugins > Installed Plugins, or use wp-cli: wp plugin list --name='the-plus-addons-for-elementor' --format=tableAffected if The plugin is installed and the displayed version is below 2.0.6
-
Confirm Elementor Page Builder is activeCheck that the Elementor website builder plugin is installed and active, as the Plus Addons extends Elementor's functionalityAffected if Elementor is active and the vulnerable version of Plus Addons is installed
-
Identify lower-privileged user accessReview WordPress user roles and capabilities to determine if contributor or author roles have access to the Elementor page editor where the Plus Addons widgets appearAffected if Contributor or author-level users can access Elementor editing and use the Plus Addons widgets
-
Inspect published content for script injectionsSearch published posts and pages for unexpected script tags, iframe elements, or event handlers (onload, onerror, onmouseover) in content fields, especially content created by lower-privileged usersAffected if Suspicious JavaScript tags or event attributes are present in published content originating from lower-privileged accounts
Your environment is affected if the Plus Addons for Elementor plugin version is below 2.0.6 and lower-privileged users have access to Elementor editing with the vulnerable widgets.
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 data2.0.6
Update The Plus Addons for Elementor Page Builder Lite to version 2.0.6 or later to patch the vulnerable widgets. Review existing content created by lower-privileged users for malicious script injections.
- 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-24266 — 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-24266 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