dbcve.org
ElementskitWordPress extension · Wpmet

CVE-2024-43996

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-23
Fix available
A fix is available. Upgrade to after 3.6.0 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in ElementsKit ElementsKit Pro allows PHP Local File Inclusion.This issue affects ElementsKit Pro: from n/a through 3.6.0.

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

Path traversal vulnerability in ElementsKit Pro WordPress plugin allows attackers to traverse directories and include arbitrary PHP files through the plugin's include functionality. This Local File Inclusion (LFI) vulnerability exists in versions up to 3.6.0 and could allow authenticated attackers to read sensitive files or potentially execute code.

MitigationUpdate ElementsKit Pro to the latest version once available. If no patch exists, implement Web Application Firewall rules to block directory traversal patterns (.., /etc/passwd) and restrict access to affected endpoints.

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

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 ElementsKit Pro is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'ElementsKit Pro' or check the plugins directory at wp-content/plugins/elementskit-pro/ for the main plugin file
    Affected if The plugin is not installed or has been removed entirely, then the vulnerability does not apply
  2. Determine installed version number
    Open the main plugin file (usually elementskit-pro.php) in the plugin directory and locate the version constant or header comment, or check in WordPress admin under Plugins > Installed Plugins > ElementsKit Pro details
    Affected if The installed version is 3.6.0 or lower, indicating the vulnerable version is present
  3. Confirm Pro version is in use
    Check the plugin name displays as 'ElementsKit Pro' (not free version) and verify the Pro-specific files exist in the elementskit-pro folder, particularly any include handler files
    Affected if Only the free version (ElementsKit) is installed without Pro functionality, the specific LFI vector may not apply
  4. Identify accessible include endpoints
    Review plugin PHP files for any include/require statements that process user-controlled parameters, particularly looking for files that handle dynamic includes (commonly in widget or template handler files)
    Affected if The plugin contains include functionality that accepts path parameters without proper sanitization, enabling directory traversal
  5. Check server logs for traversal attempts
    Review web server access logs (Apache error.log, Nginx error.log) and WordPress debug logs for patterns containing '../', '..\', or attempts to include files from outside the plugin directory, particularly around ElementsKit Pro endpoints
    Affected if Recent or historical requests contain directory traversal patterns targeting the plugin's include functionality

A user is affected if ElementsKit Pro version 3.6.0 or lower is installed and the vulnerable include functionality is accessible to authenticated users.

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 a release after 3.6.0
Interim mitigation

Update ElementsKit Pro to the latest version once available. If no patch exists, implement Web Application Firewall rules to block directory traversal patterns (.., /etc/passwd) and restrict access to affected endpoints.

Recommended fix Moderate confidence

ElementsKit Pro 3.6.1 or later

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate ElementsKit Pro in the plugin list
  4. 4. If an update is available, click 'Update Now' to update ElementsKit Pro to the latest version
  5. 5. After updating, verify the plugin version is 3.6.1 or higher
  6. 6. Test that ElementsKit Pro functionality works correctly on your site

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

Fix this in Elementskit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.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-43996 — 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-43996 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