Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-6455 Overview
CVE-2024-6455 is an information exposure vulnerability in the ElementsKit Elementor addons plugin for WordPress. All versions up to and including 3.2.0 are affected. The flaw resides in the ekit_widgetarea_content function, which lacks capability checks before returning content. Unauthenticated attackers can view any item created in Elementor, including posts, pages, and templates in draft, pending, or private states. The issue is tracked under [CWE-200] Information Exposure and [CWE-862] Missing Authorization.
Critical Impact
Unauthenticated remote attackers can read unpublished WordPress content, including private posts, drafts, and templates that may contain sensitive business data or credentials.
Affected Products
- Wpmet ElementsKit Elementor Addons (Lite) — all versions through 3.2.0
- WordPress sites running the elementskit-lite plugin
- Any Elementor-based site relying on ElementsKit widget area rendering
Discovery Timeline
- 2024-07-18 - CVE-2024-6455 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-6455
Vulnerability Analysis
The ElementsKit plugin registers an AJAX handler that renders widget area content on demand. The ekit_widgetarea_content function accepts a post identifier and returns the corresponding Elementor content. The handler does not verify whether the requesting user has permission to view the referenced item. As a result, any network-based caller can retrieve rendered content for arbitrary post IDs, regardless of the underlying post status.
This behavior turns a rendering utility into a broad content-disclosure primitive. Attackers can enumerate post IDs and harvest unpublished material, including draft blog posts, unreleased marketing pages, private customer-only content, and internal Elementor templates.
Root Cause
The root cause is a missing authorization check inside ekit_widgetarea_content, defined in modules/controls/widget-area-utils.php. The function does not call current_user_can() or validate the post status against the requester's capabilities before returning content. The relevant source is available in the WordPress ElementsKit Widget Utility.
Attack Vector
Exploitation is network-based and requires no authentication or user interaction. An attacker sends a crafted request to the WordPress AJAX endpoint invoking the ekit_widgetarea_content action with a target post ID. The server responds with the rendered Elementor content for that post, bypassing WordPress visibility controls for draft, pending, and private states. Detailed technical context is available in the Wordfence Vulnerability Report.
No verified public proof-of-concept code is referenced in the advisory. The vulnerability mechanism is described in prose above; see the linked advisory for reproduction details.
Detection Methods for CVE-2024-6455
Indicators of Compromise
- Unauthenticated POST or GET requests to /wp-admin/admin-ajax.php with the action=ekit_widgetarea_content parameter.
- Sequential enumeration of post ID values in AJAX request parameters from a single source IP.
- Access log entries for admin-ajax.php returning large response bodies to unauthenticated sessions.
Detection Strategies
- Inspect web server access logs for requests targeting the ekit_widgetarea_content AJAX action without a valid wordpress_logged_in_* cookie.
- Correlate spikes in admin-ajax.php traffic with anomalous post-ID enumeration patterns.
- Deploy WAF rules that flag or block unauthenticated calls to ElementsKit widget-area endpoints.
Monitoring Recommendations
- Alert on repeated unauthenticated requests to admin-ajax.php referencing ElementsKit actions.
- Monitor for outbound data volume anomalies from the WordPress host that align with content-scraping behavior.
- Track installed ElementsKit versions across the WordPress fleet and alert on any instance at or below 3.2.0.
How to Mitigate CVE-2024-6455
Immediate Actions Required
- Update the ElementsKit Elementor addons plugin to a version later than 3.2.0.
- Audit all draft, pending, and private Elementor items for sensitive data that may have been exposed.
- Rotate any credentials, API keys, or internal URLs that were stored in unpublished Elementor content.
Patch Information
The vendor addressed CVE-2024-6455 in ElementsKit releases after 3.2.0 by adding capability checks to the ekit_widgetarea_content handler. Administrators should upgrade through the WordPress plugin manager or by replacing the plugin files with the latest release from the WordPress plugin repository. Confirm the running version under Plugins > Installed Plugins after the upgrade.
Workarounds
- If immediate patching is not possible, deactivate the ElementsKit plugin until the update can be applied.
- Block unauthenticated requests to admin-ajax.php with action=ekit_widgetarea_content at the WAF or reverse proxy.
- Restrict access to /wp-admin/admin-ajax.php from untrusted networks where feasible using IP allowlisting.
# Example WAF rule (ModSecurity) to block unauthenticated ekit_widgetarea_content requests
SecRule REQUEST_URI "@contains /wp-admin/admin-ajax.php" \
"chain,phase:2,deny,status:403,id:1006455,msg:'Block CVE-2024-6455 ElementsKit unauthenticated widget-area access'"
SecRule ARGS:action "@streq ekit_widgetarea_content" \
"chain"
SecRule &REQUEST_COOKIES:/wordpress_logged_in_/ "@eq 0"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

