dbcve.org
Premium Addons For ElementorWordPress extension · Leap13

CVE-2024-24831

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-10
Fix available
A fix is available. Upgrade to 4.10.17 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Leap13 Premium Addons for Elementor premium-addons-for-elementor.This issue affects Premium Addons for Elementor: from n/a through <= 4.10.16.

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 · moderate confidence

A stored Cross-site Scripting (XSS) vulnerability in Premium Addons for Elementor allows attackers to inject malicious JavaScript code through improper input sanitization. This affects versions up to and including 4.10.16. The vulnerability occurs during web page generation when user-supplied input is not adequately neutralized before being rendered in the browser.

MitigationUpdate to the latest version of Premium Addons for Elementor when a patch is released. In the meantime, restrict usage of the affected plugin to trusted users only and implement Content Security Policy (CSP) headers as a defense-in-depth measure.

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

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
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 checks

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

  1. Verify Premium Addons for Elementor is installed
    Check the WordPress plugin directory or inspect the plugin files for 'premium-addons-for-elementor' folder. In WordPress admin, go to Plugins > Installed Plugins and look for 'Premium Addons for Elementor'.
    Affected if The plugin is not found in the WordPress installation.
  2. Determine installed version number
    In WordPress admin, go to Plugins > Installed Plugins > Premium Addons for Elementor and read the version number displayed below the plugin name. Alternatively, check the main plugin PHP file header for the 'Version' tag.
    Affected if The installed version is any version less than 4.10.17 (including 4.10.16 and earlier).
  3. Confirm plugin is active on the site
    In WordPress admin, go to Plugins > Installed Plugins and verify that Premium Addons for Elementor shows as 'Active' rather than 'Inactive' or 'Must Use'.
    Affected if The plugin is active and running in the production environment.
  4. Check if user-generated content is handled by the plugin
    Review Elementor page templates and widgets in use. Inspect any frontend pages that use Premium Addons widgets and contain user-supplied input (forms, comments, user profile fields, or custom content areas). Use browser developer tools to examine the HTML source of rendered pages.
    Affected if The plugin is actively rendering pages that contain user-supplied input without additional sanitization layers.

A user is affected if Premium Addons for Elementor is installed and active with a version lower than 4.10.17, and the site processes user-supplied content through the plugin's widgets.

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.17 or later
Fixed in 4.10.17
Interim mitigation

Update to the latest version of Premium Addons for Elementor when a patch is released. In the meantime, restrict usage of the affected plugin to trusted users only and implement Content Security Policy (CSP) headers as a defense-in-depth measure.

Recommended fix High confidence

4.10.17 or later

  1. Backup your WordPress site before updating
  2. Update Premium Addons for Elementor to version 4.10.17 or later through the WordPress plugin admin panel, or download and install the latest version from the WordPress plugin repository

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

Fix this in Premium Addons For Elementor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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