dbcve.org
ElementskitWordPress extension · Wpmet

CVE-2024-3500

HIGH · 8.8 CVSS v3.1 Published 2024-05-02
Fix available
A fix is available. Upgrade to 3.6.1 or later.
See remediation →
94/100
Remediation priority · Urgent
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 ElementsKit Pro plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.6.0 via the Price Menu, Hotspot, and Advanced Toggle widgets. This makes it possible for authenticated attackers, with contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. CVE-2024-43996 is potentially a duplicate of this issue.

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

The ElementsKit Pro WordPress plugin is vulnerable to Local File Inclusion in versions up to 3.6.0. The flaw exists in the Price Menu, Hotspot, and Advanced Toggle widgets, allowing authenticated attackers with contributor-level access or higher to include and execute arbitrary files on the server, leading to PHP code execution.

MitigationUpdate ElementsKit Pro to version 3.6.1 or later immediately. Review all user accounts with contributor-level or higher access and ensure no unauthorized files exist on the server.

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
ElementskitWordPress extension
Affected:< 3.6.1

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 ElementsKit Pro plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'ElementsKit Pro' or check the wp-content/plugins directory for elementskit-pro folder
    Affected if The plugin is not found, so the CVE does not apply
  2. Check installed version of ElementsKit Pro
    In WordPress admin_plugins page, find ElementsKit Pro and note the version number displayed; or check version in elementskit-pro/elementskit.php file header
    Affected if Version is 3.6.0 or lower (versions below 3.6.1 are affected)
  3. Identify use of affected widgets
    Check pages, posts, or templates where Price Menu, Hotspot, or Advanced Toggle widgets from ElementsKit have been added using the WordPress block editor or Elementor page builder
    Affected if Any of these three widgets (Price Menu, Hotspot, Advanced Toggle) are in use on the site
  4. Verify contributor-level or higher user accounts exist
    In WordPress admin, go to Users > All Users and review user roles; check for accounts with Contributor, Author, Editor, or Administrator roles
    Affected if There are user accounts with contributor-level or higher access (these roles can exploit the vulnerability)

If ElementsKit Pro version is 3.6.0 or below AND any of the three affected widgets are in use AND there are contributor-level or higher users on the site, the environment is vulnerable to CVE-2024-3500.

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.6.1 or later
Fixed in 3.6.1
Interim mitigation

Update ElementsKit Pro to version 3.6.1 or later immediately. Review all user accounts with contributor-level or higher access and ensure no unauthorized files exist on the server.

Recommended fix High confidence

ElementsKit Pro 3.6.1

  1. 1. Back up your WordPress site (database and files) before making any changes
  2. 2. Navigate to Dashboard > Plugins in your WordPress admin panel
  3. 3. Locate the ElementsKit Pro plugin in the installed plugins list
  4. 4. If automatic updates are enabled, the plugin should update to 3.6.1 automatically; otherwise, click 'Update Now'
  5. 5. If an update is not available, manually download version 3.6.1 from the official ElementsKit source (account.wpmet.com) or the WordPress plugin repository
  6. 6. Deactivate the current ElementsKit Pro plugin, then delete it (this removes the old files)
  7. 7. Upload and install the version 3.6.1 plugin package
  8. 8. Reactivate the ElementsKit Pro plugin
Caveat Review the ElementsKit Pro 3.6.1 changelog for any feature changes or deprecations before upgrading in production environments

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

Fix this in Elementskit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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