dbcve.org
Elements Kit Elementor AddonsWordPress extension · Wpmet

CVE-2024-32505

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-17
Fix available
A fix is available. Upgrade to 3.0.7 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 Roxnor ElementsKit Elementor addons Lite elementskit-lite.This issue affects ElementsKit Elementor addons Lite: from n/a through <= 3.0.6.

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

This is a Cross-site Scripting (XSS) vulnerability in the ElementsKit Elementor addons Lite WordPress plugin. The vulnerability stems from improper neutralization of input during web page generation, allowing an attacker to inject malicious scripts into pages rendered by the plugin. The issue affects all versions through 3.0.6.

MitigationUpdate ElementsKit Lite to the latest version which should contain proper input sanitization and output encoding. Until then, limit user access to trusted roles only and consider additional WAF protections for the wp-admin area.

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
Elements Kit Elementor AddonsWordPress extension
Affected:< 3.0.7

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 the ElementsKit Lite plugin version
    In the WordPress admin, go to Plugins > Installed Plugins and find 'ElementsKit Elementor Addon' or 'Wpmet Elements Kit'. The version number is displayed under the plugin name. Alternatively, access your site via FTP/SFTP and read the main plugin file header (commonly named like elementskit-lite.php or similar) to find the 'Version' field in the plugin metadata.
    Affected if The displayed version is lower than 3.0.7 (for example, 3.0.6, 3.0.5, 2.0.0, etc.) or if no version number is shown (indicating an old installation).
  2. Verify the plugin is currently active
    In WordPress admin, go to Plugins > Installed Plugins and confirm that the ElementsKit Lite plugin has an 'Active' status indicator (usually a blue 'Activate' link or a green 'Active' badge).
    Affected if The plugin is active and the version is below 3.0.7.
  3. Identify user roles with access to Elementor editor
    In WordPress admin, go to Users > Users or Users > User Roles (if using a role editor plugin). Review which user roles have the capability to use the Elementor page builder, as ElementsKit extends Elementor functionality. Check for roles like Editor, Author, Contributor, or custom roles that may have 'edit_posts' or 'use_elementor' capabilities.
    Affected if Untrusted roles such as Subscriber, Contributor, or Author have access to the Elementor editor, and the plugin version is below 3.0.7.

Your environment is affected if the ElementsKit Lite plugin version is below 3.0.7 and the plugin is active, regardless of user role configuration.

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 3.0.7 or later
Fixed in 3.0.7
Interim mitigation

Update ElementsKit Lite to the latest version which should contain proper input sanitization and output encoding. Until then, limit user access to trusted roles only and consider additional WAF protections for the wp-admin area.

Recommended fix High confidence

3.0.7

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find 'ElementsKit Elementor Addons Lite' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 3.0.7 of the plugin
  5. After updating, clear any caching plugins or server-side caches
  6. Verify the plugin version shows 3.0.7 in the WordPress plugins list

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

Fix this in Elements Kit Elementor Addons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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