Premium Addons For ElementorWordPress extension · Leap13

CVE-2024-1242

MEDIUM · 6.4 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to 4.10.19 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 button onclick attribute in all versions up to, and including, 4.10.18 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor 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

Premium Addons for Elementor plugin for WordPress versions up to 4.10.18 contain a stored XSS vulnerability in the button onclick attribute due to insufficient input sanitization and output escaping. Authenticated attackers with contributor-level access or higher can inject arbitrary JavaScript that executes when users view injected pages.

MitigationUpdate the Premium Addons for Elementor plugin to version 4.10.19 or later, which includes proper sanitization of the onclick attribute value and output escaping.

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.19

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, find 'Premium Addons for Elementor' by Leap13, and note the version number displayed
    Affected if The installed version is earlier than 4.10.19 (versions up to 4.10.18 are affected)
  2. Verify user access level
    Check if any user accounts have Contributor-level or higher access to the WordPress admin
    Affected if At least one user with Contributor-level or higher access exists in the system
  3. Identify button widget usage
    Review pages and posts created with Elementor that use the Premium Addons button widget, particularly those with custom onclick attributes
    Affected if Pages or posts contain button widgets from Premium Addons with custom onclick JavaScript
  4. Inspect page source for XSS payload
    View the HTML source of pages using the Premium Addons button widget and search for the onclick attribute to see if user-supplied values are properly escaped
    Affected if The onclick attribute contains unescaped quotes or raw user input without proper sanitization

Your environment is affected if the Premium Addons for Elementor plugin version is below 4.10.19 and you have content using the button widget with custom onclick attributes accessible to users with contributor-level permissions.

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.19 or later
Fixed in 4.10.19
Interim mitigation

Update the Premium Addons for Elementor plugin to version 4.10.19 or later, which includes proper sanitization of the onclick attribute value and output escaping.

Recommended fix High confidence

Premium Addons For Elementor 4.10.19

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Premium Addons For Elementor in the plugin list
  4. Check if the current version is below 4.10.19
  5. If vulnerable, click Update Now on the Premium Addons For Elementor plugin
  6. Verify the update completed successfully
  7. Confirm the new version is 4.10.19 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Premium Addons For Elementor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1242 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1242 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