ElementsKit Elementor addons <= 3.2.0 - Unauthenticated Information Exposure via ekit_widgetarea_content Function
Strategic Overview
- Status
- Patched in 3.2.1
- Affected Version
<= 3.2.0- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2024-6455
At a glance
CVE-2024-6455 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the ElementsKit Elementor Addons WordPress plugin, affecting versions <= 3.2.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.2.1; sites on affected versions should update now. Disclosed July 2024, reported by stealthcopter.
Vulnerability Overview
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 Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in ElementsKit Elementor Addons <= 3.2.0 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For ElementsKit Elementor Addons the fix is 3.2.1: builds <= 3.2.0 are affected, anything from 3.2.1 onward is not.
Remediation
Update to version 3.2.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: ElementsKit Elementor Addons 3.2.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in ElementsKit Elementor Addons – Advanced Widgets & Templates Addons for Elementor
- 8.8CVE-2024-3499: ElementsKit Elementor addons <= 3.1.0 LFI
CVE-2024-3499 - 8.8CVE-2024-2047: ElementsKit Elementor addons <= 3.0.6 LFI in render_raw
CVE-2024-2047 - 7.2CVE-2026-13392: ElementsKit Elementor Addons RCE
CVE-2026-13392 - 6.5CVE-2026-4362: ElementsKit… Unauthenticated Widget Content Overwrite
CVE-2026-4362 - 6.4CVE-2026-13393: ElementsKit Lite <= 3.10.0 Stored Cross-Site Scripting
CVE-2026-13393 - 6.4CVE-2026-2600: ElementsKit Elementor Addons and Templates Stored XSS
CVE-2026-2600 - 6.4CVE-2025-3614: ElementsKit Elementor Addons and Templates Stored XSS
CVE-2025-3614 - 6.4CVE-2025-4479: ElementsKit Lite <= 3.5.2 Stored Cross-Site Scripting
CVE-2025-4479
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C