dbcve.org
Premium Addons For ElementorWordPress extension · Leap13

CVE-2024-37922

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-20
Fix available
A fix is available. Upgrade to 4.10.35 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.34.

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

Reflected XSS vulnerability in Premium Addons for Elementor allows attackers to inject malicious JavaScript via unsanitized user input that gets rendered in web pages without proper output encoding.

MitigationUpdate to the latest version of Premium Addons for Elementor if a patched release is available; otherwise implement input validation/sanitization on all user-supplied parameters and deploy WAF rules to block XSS attack patterns.

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

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. Locate Premium Addons for Elementor version
    In WordPress admin, go to Plugins > Installed Plugins > Premium Addons for Elementor and read the version number displayed under the plugin name
    Affected if The displayed version is lower than 4.10.35
  2. Verify version via plugin files
    Access the plugin main file (typically /wp-content/plugins/premium-addons-for-elementor/premium-addons-for-elementor.php) and locate the 'Version' header comment
    Affected if The Version header shows a number less than 4.10.35
  3. Confirm plugin is active
    Check WordPress admin Plugins page to verify Premium Addons for Elementor is currently activated
    Affected if Plugin is active and version is below 4.10.35
  4. Identify user input reflection points
    Review website pages that use Premium Addons widgets and inspect page source (right-click > View Page Source) for any URL parameters or form inputs that appear in the HTML output
    Affected if User-supplied parameters are reflected in HTML without encoding (visible as raw input in source)
  5. Test for XSS vulnerability indicators
    Temporarily inject a benign test string such as <script>alert(1)</script> into URL parameters on pages using Premium Addons widgets, then check if the script tag renders as plain text or gets executed in the page
    Affected if The test string appears unescaped in the page HTML or executes as JavaScript

You are affected if Premium Addons for Elementor is active and the installed version is below 4.10.35, especially if user input parameters are reflected in pages without HTML encoding.

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.35 or later
Fixed in 4.10.35
Interim mitigation

Update to the latest version of Premium Addons for Elementor if a patched release is available; otherwise implement input validation/sanitization on all user-supplied parameters and deploy WAF rules to block XSS attack patterns.

Recommended fix High confidence

Premium Addons For Elementor version 4.10.35 or later

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins
  3. Locate Premium Addons for Elementor in the plugins list
  4. Click 'Update now' to upgrade to the latest version (4.10.35 or higher)
  5. Verify the update completed successfully by checking the plugin version
  6. Clear any caching plugins or server-side caches to ensure the patched version is served

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-37922 — 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-37922 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