Premium Addons For ElementorWordPress extension · Leap13
CVE-2024-32791
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 · uneditedImproper 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.25.
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 confidenceCross-site Scripting (XSS) vulnerability in Leap13 Premium Addons for Elementor plugin allows attackers to inject malicious scripts into web pages generated by the plugin through improper input neutralization, potentially executing in users' browsers.
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.26CVSS 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 plugin installationAccess your WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for Leap13 Premium Addons For Elementor or Premium Addons for Elementor in the plugin list.Affected if The plugin is present in your WordPress installation
-
Identify installed versionIn the Plugins list, locate the version number displayed beneath the plugin name. Alternatively, inspect the plugin's main PHP file header in wp-content/plugins/premium-addons-for-elementor/ for the Version field.Affected if You can determine a specific version number from the plugin
-
Compare against affected rangeCompare your installed version number to the affected range: any version less than 4.10.26 is vulnerable. For example, 4.10.25, 4.10.0, 4.9.0, or earlier versions are all within the affected range.Affected if Installed version is numerically less than 4.10.26
You are affected if Premium Addons for Elementor is installed and its version is below 4.10.26.
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.26
Update Premium Addons for Elementor to version 4.10.26 or later which contains the security patch. Until updated, restrict administrative access to the plugin and consider deploying a WAF rule to filter XSS attack patterns.
Premium Addons for Elementor 4.10.26
- Backup your WordPress site before making any changes
- Update Premium Addons for Elementor to version 4.10.26 or later through the WordPress dashboard (Plugins > Add New > Upload or directly from the WordPress plugin repository)
- Alternatively, update via WordPress admin: go to Dashboard > Updates or navigate to Plugins > Installed Plugins and update Premium Addons for Elementor
- Verify the update was successful by checking the plugin version in Plugins > Installed Plugins
- Clear any caching plugins or server-side caches after the update
- Test the site frontend and Elementor editor to ensure functionality is intact
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Premium Addons For Elementor
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32791 — 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-32791 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