dbcve.org
Elements Kit Elementor AddonsWordPress extension · Wpmet

CVE-2024-6455

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-18
Fix available
A fix is available. Upgrade to 3.2.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Elementor addons plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 3.2.0 due to a missing capability checks on ekit_widgetarea_content function. This makes it possible for unauthenticated attackers to view any item created in Elementor, such as posts, pages and templates including drafts, pending and private items.

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 plugin for WordPress has a missing capability check on the ekit_widgetarea_content function, allowing unauthenticated attackers to retrieve any Elementor-created content including drafts, pending review, and private items by directly accessing the vulnerable function.

MitigationUpdate ElementsKit plugin to version 3.2.1 or later which includes proper capability verification, or add WordPress capability checks (like current_user_can('edit_posts')) to the ekit_widgetarea_content function.

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.2.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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Confirm ElementsKit plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Wpmet Elements Kit' or 'ElementsKit' in the installed plugins list
    Affected if Plugin is not found in the installed plugins list, then not affected by this CVE
  2. Identify installed ElementsKit version
    In Plugins page, click 'View Details' on ElementsKit or check the plugin header in /wp-content/plugins/elements-kit-lite/ or similar directory for the 'Version' field
    Affected if Version is present and less than 3.2.1 (for example, 3.2.0, 3.1.x, 3.0.x, etc.)
  3. Verify vulnerable function exists
    Search plugin files for the function 'ekit_widgetarea_content' using grep or a file search in the elements-kit plugin directory under /wp-content/plugins/
    Affected if The function 'ekit_widgetarea_content' is found in the plugin files and the version is below 3.2.1
  4. Test unauthenticated access to the function
    Use a tool like curl to send a request to the AJAX endpoint or direct access point that calls ekit_widgetarea_content without providing authentication cookies
    Affected if The function responds with content (including drafts, pending, or private items) without requiring login credentials

You are affected if ElementsKit plugin version is below 3.2.1 and the ekit_widgetarea_content function is accessible without authentication.

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.2.1 or later
Fixed in 3.2.1
Interim mitigation

Update ElementsKit plugin to version 3.2.1 or later which includes proper capability verification, or add WordPress capability checks (like current_user_can('edit_posts')) to the ekit_widgetarea_content function.

Recommended fix High confidence

Elements Kit Elementor Addons version 3.2.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the ElementsKit Elementor Addons plugin
  4. Check if the current version is below 3.2.1
  5. If update available, click 'Update Now' to upgrade to version 3.2.1
  6. Alternatively, navigate to Dashboard > Updates and apply available updates
  7. Verify the plugin is now running version 3.2.1 after the update completes

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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