CVE-2021-24271
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 “Ultimate Addons for Elementor” WordPress Plugin before 1.30.0 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 confidenceStored XSS vulnerability in the Ultimate Addons for Elementor WordPress plugin affecting multiple widgets. Lower-privileged users such as contributors can inject malicious JavaScript code through these widgets, which executes when other users view the compromised content in the Elementor page builder.
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< 1.30.0CVSS 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 Ultimate Addons for Elementor is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Ultimate Addons for Elementor' by Brainstormforce. Note the installed version displayed.Affected if Plugin is present with version below 1.30.0
-
Confirm the installed version numberCheck the version number displayed next to the plugin name in the WordPress plugins list. Compare it against the affected range: versions prior to 1.30.0.Affected if Version number is less than 1.30.0 (for example, 1.29.0, 1.28.2, etc.)
-
Identify active Ultimate Addons widgetsOpen a page or post in the Elementor editor. In the widget panel, scroll through available widgets and note which ones belong to the Ultimate Addons category and are currently placed on the page.Affected if Any Ultimate Addons widgets are being used in published content
-
Check for lower-privileged user accessNavigate to Users > All Users in WordPress admin. Review the roles assigned to users who can access the Elementor editor (such as Contributors, Authors, or Editors).Affected if Users with Contributor role or other lower-privileged roles have access to create or edit content using Elementor
Your environment is affected if the Ultimate Addons for Elementor plugin is installed with a version below 1.30.0 and any of its widgets are being used while lower-privileged users have editing permissions.
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.30.0
Update the Ultimate Addons for Elementor plugin to version 1.30.0 or later. If immediate update is not possible, disable the affected widgets or restrict user editing permissions until the patch can be applied.
- 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-24271 — 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-24271 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