Premium Addons For ElementorWordPress extension · Leap13
CVE-2021-24257
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 “Premium Addons for Elementor” WordPress Plugin before 4.2.8 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 Premium Addons for Elementor WordPress plugin before version 4.2.8 contains multiple widgets vulnerable to stored XSS. Lower-privileged users such as contributors can inject malicious JavaScript payloads through these widgets, which execute when other users view the compromised pages 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
Premium Addons For ElementorWordPress extension
< 4.2.8CVSS 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 Premium Addons for Elementor is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Premium Addons for Elementor' by Leap13Affected if The plugin is listed and active on the site
-
Check the installed version numberIn Plugins list, locate the version number displayed under the plugin name. Alternatively, check the plugin header in /wp-content/plugins/premium-addons-for-elementor/elementor.phpAffected if Version is below 4.2.8 (for example, 4.2.7 or earlier)
-
Identify if any Premium Addons widgets are in useIn WordPress admin, review pages and posts that use the Elementor page builder. Check if any widgets from the Premium Addons plugin have been added to these pagesAffected if Pages contain widgets from the Premium Addons plugin and the plugin version is vulnerable
-
Inspect pages for suspicious script injectionsView page source or use browser developer tools to examine the HTML output of pages built with Elementor. Look for unexpected <script> tags, event handlers like onload/onerror, or encoded JavaScript in widget content areasAffected if Unexpected script tags or XSS payloads are present in the rendered output of pages using Premium Addons widgets
If the Premium Addons for Elementor plugin version is below 4.2.8 and any of its widgets are in use on pages, the environment is affected by this stored XSS vulnerability.
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.2.8
Update the Premium Addons for Elementor plugin to version 4.2.8 or later. Review existing pages for any injected XSS payloads and clean them. Consider restricting widget usage permissions until the update is applied.
Fix this in Premium Addons For Elementor
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24257 — 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-24257 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