dbcve.org
Premium Addons For ElementorWordPress extension · Leap13

CVE-2024-2665

MEDIUM · 6.4 CVSS v3.1 Published 2024-04-10
Fix available
A fix is available. Upgrade to 4.10.28 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The Premium Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's button in all versions up to, and including, 4.10.27 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.

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 confidence

The Premium Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) in its button widget. Authenticated attackers with contributor-level access or higher can inject arbitrary JavaScript through unsanitized user-supplied attributes. The injected scripts execute whenever users access pages containing the compromised button element.

MitigationUpdate Premium Addons for Elementor to version 4.10.28 or later which contains proper input sanitization and output escaping. Until patched, audit existing pages for suspicious button widget configurations and consider limiting contributor-level user permissions.

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
Affected:< 4.10.28

CVSS 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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins. Locate 'Premium Addons for Elementor' and read the version number from the plugin description. Alternatively, check the main plugin file (premium-addons-for-elementor.php) for the 'Version' header comment.
    Affected if The version number displayed is less than 4.10.28 (for example, 4.10.27 or earlier).
  2. Verify button widget usage
    In Elementor editor, search for 'Premium Button' or 'Button' widget in the widget panel. Check published pages by viewing page source or using a site search for 'premium-button' or 'pa-button' CSS classes.
    Affected if The Premium Addons button widget is present and actively used on any published page or post on the site.
  3. Review contributor-level user accounts
    In WordPress admin, go to Users > All Users. Look for any user accounts with the 'Contributor' role.
    Affected if At least one user account with contributor-level permissions exists on the site.
  4. Audit button widget link attributes
    In Elementor editor, open any page containing a Premium Button widget. Click the widget and expand the Link section in the widget panel. Check the Link URL, Text, and any custom attributes for unsanitized or unexpected content such as javascript: alerts, or HTML tags.
    Affected if Button widget link fields contain unsanitized user-supplied content including raw HTML, script tags, or javascript: protocol handlers.

You are affected if the installed Premium Addons for Elementor version is below 4.10.28 AND the button widget is used on your site AND (optionally) contributor-level user accounts exist who could exploit this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.10.28 or later
Fixed in 4.10.28
Interim mitigation

Update Premium Addons for Elementor to version 4.10.28 or later which contains proper input sanitization and output escaping. Until patched, audit existing pages for suspicious button widget configurations and consider limiting contributor-level user permissions.

Recommended fix High confidence

Premium Addons For Elementor version 4.10.28

  1. Navigate to WordPress dashboard > Plugins > Installed Plugins
  2. Locate Premium Addons For Elementor
  3. Click 'Update now' when version 4.10.28 or later is available
  4. Verify the update was successful by checking the plugin version

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2665 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-2665 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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