Premium Addons For ElementorWordPress extension · Leap13
CVE-2024-2666
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 plugin for WordPress is vulnerable to DOM-Based Stored Cross-Site Scripting via the plugin's Bullet List Widget in all versions up to, and including, 4.10.24 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page and attempts to edit the content.
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 plugin for WordPress versions up to 4.10.24 contain a stored DOM-based XSS vulnerability in the Bullet List Widget. Authenticated attackers with contributor-level access can inject malicious JavaScript through unsanitized user-supplied attributes, which executes when other users access or edit the compromised page.
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.10.25CVSS 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 installedNavigate to WordPress Admin > Plugins and locate Premium Addons for Elementor in the installed plugins listAffected if The plugin is not listed means it is not installed and therefore not affected
-
Check the installed plugin versionIn the Plugins list, view the plugin details or check the plugin header file for the version number. Compare it to the affected range: versions prior to 4.10.25 are vulnerableAffected if Installed version is less than 4.10.25 means the plugin version is affected
-
Identify pages using the Bullet List WidgetSearch your WordPress pages and posts for instances of the Bullet List Widget from the Premium Addons plugin. This can be done by reviewing page content or using a database query to find postmeta entries containing 'premium-bullet-list' or similar widget identifiersAffected if No instances of the Bullet List Widget are found means the specific vulnerable component is not in use
-
Inspect Bullet List Widget settings for unsanitized attributesEdit each page containing the Bullet List Widget and examine the widget settings panel. Review all text fields including titles, descriptions, and list item content for suspicious script tags, event handlers (onclick, onload, onerror), or unusual JavaScript codeAffected if Any Bullet List Widget contains unsanitized or encoded user-supplied attributes that could execute JavaScript when the page is viewed means the page is likely compromised
-
Review page source for injected scriptsView the source code of published pages containing the Bullet List Widget and search for <script> tags, javascript: URLs, or event handler attributes within the widget output areaAffected if Unexpected script tags or event handlers are present in the rendered Bullet List Widget output means the vulnerability has been exploited
A user is affected if Premium Addons for Elementor version 4.10.24 or lower is installed AND the Bullet List Widget is in use with unsanitized attributes that could execute malicious JavaScript
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.
dbcve · scoped4.10.25
Update the Premium Addons for Elementor plugin to a version beyond 4.10.24, and review existing pages using the Bullet List Widget for any injected malicious scripts.
Premium Addons For Elementor version 4.10.25
- Backup your WordPress site before making any changes
- Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
- Locate Premium Addons For Elementor in the plugins list
- If an update is available, click 'Update Now' to update the plugin to version 4.10.25
- Alternatively, you can manually upload version 4.10.25 of the plugin from the WordPress plugin repository
- After updating, verify the plugin version shows 4.10.25 in the plugins list
- Clear any caching plugins or server-side caches
- Test the Bullet List Widget functionality to ensure the update did not break existing content
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Premium Addons For Elementor
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2666 — 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-2024-2666 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