Skip to main content
Vulnerability Database/CVE-2024-37255

CVE-2024-37255: ElementsKit Elementor Auth Bypass Flaw

CVE-2024-37255 is an authorization bypass vulnerability in ElementsKit Elementor addons that allows unauthorized access to restricted functions. This post explains the security impact, affected versions, and mitigation steps.

Published:

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-37255 Overview

CVE-2024-37255 is a Missing Authorization vulnerability [CWE-862] in the ElementsKit Elementor addons Lite plugin for WordPress, developed by Roxnor (Wpmet). The flaw affects all versions up to and including 3.1.4 of the elementskit-lite plugin. Unauthenticated attackers can reach plugin functionality that should be restricted by capability or nonce checks. The issue is categorized as broken access control and is remotely exploitable over the network without user interaction.

Critical Impact

Unauthenticated remote attackers can invoke protected plugin actions and modify limited integrity state on affected WordPress sites running ElementsKit Elementor addons Lite <= 3.1.4.

Affected Products

  • Wpmet ElementsKit Elementor addons Lite (elementskit-lite) versions up to and including 3.1.4
  • WordPress sites with the ElementsKit Lite plugin installed and activated
  • Hosting environments exposing the WordPress REST API or admin-ajax.php to the public internet

Discovery Timeline

  • 2024-11-01 - CVE-2024-37255 published to the National Vulnerability Database (NVD)
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-37255

Vulnerability Analysis

The vulnerability is a Missing Authorization issue in the ElementsKit Elementor addons Lite plugin. The affected plugin exposes one or more handlers that execute without verifying the caller's capability level. Attackers reach these handlers through standard WordPress request surfaces such as admin-ajax.php or the REST API. Because no authentication is required, exploitation does not depend on a compromised user account or administrative role.

The impact is limited to integrity, with no direct confidentiality or availability loss observed. However, in composite attack chains, broken access control in page builder addons commonly enables content tampering, injected widget configurations, or abuse of plugin features intended for authenticated editors.

Root Cause

The root cause is a missing capability or nonce check on a sensitive endpoint inside the elementskit-lite codebase. WordPress requires plugin developers to gate privileged actions with functions such as current_user_can() and check_ajax_referer(). In the affected versions, one or more plugin action handlers execute their logic before performing these checks, allowing unauthenticated callers to trigger them.

Attack Vector

The attack vector is network-based and requires no privileges or user interaction. An attacker sends crafted HTTP requests to the WordPress site targeting the vulnerable plugin action. The vulnerability manifests in the request-handling path of the plugin. Refer to the Patchstack Vulnerability Report for endpoint-specific technical details.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2024-37255

Indicators of Compromise

  • Unauthenticated POST requests to /wp-admin/admin-ajax.php with action parameters referencing ElementsKit handlers
  • Requests to WordPress REST routes under namespaces registered by elementskit-lite originating from unauthenticated sessions
  • Unexpected modifications to Elementor page or widget metadata without a corresponding editor login event
  • Spikes in 200-response traffic to plugin endpoints from single IPs or distributed scanning infrastructure

Detection Strategies

  • Inventory WordPress installations and flag any instance of elementskit-lite at version 3.1.4 or earlier
  • Enable WordPress debug and access logging to capture admin-ajax.php and REST API calls with their action and route parameters
  • Correlate plugin endpoint access with session authentication state to surface anonymous invocations of privileged actions
  • Deploy web application firewall (WAF) rules that match the ElementsKit action names identified in the Patchstack advisory

Monitoring Recommendations

  • Alert on anonymous requests to ElementsKit AJAX actions and REST routes
  • Track plugin version drift across managed WordPress fleets to detect unpatched installs
  • Review Elementor revision history for unexplained changes to widgets or templates
  • Forward WordPress and reverse-proxy logs into a centralized data lake for retention and correlation

How to Mitigate CVE-2024-37255

Immediate Actions Required

  • Update ElementsKit Elementor addons Lite to a version released after 3.1.4 that resolves the Missing Authorization issue
  • If immediate patching is not possible, deactivate and remove the elementskit-lite plugin
  • Restrict access to /wp-admin/ and admin-ajax.php from untrusted networks where feasible
  • Audit recent Elementor content and plugin option changes for unauthorized modifications

Patch Information

Upgrade the elementskit-lite plugin to a fixed release above version 3.1.4. Consult the Patchstack Vulnerability Report and the plugin's official WordPress.org changelog for the specific fixed version and release notes.

Workarounds

  • Place the WordPress site behind a WAF and block requests invoking the affected ElementsKit actions until the plugin is patched
  • Enforce IP allow-listing on /wp-admin/ paths for administrators and editors
  • Disable the plugin on sites that do not actively use ElementsKit features
  • Enable file integrity monitoring on the wp-content/plugins/elementskit-lite/ directory to detect tampering
bash
# Example: block anonymous access to known ElementsKit AJAX actions at the web server (nginx)
location = /wp-admin/admin-ajax.php {
    if ($arg_action ~* "^(elementskit_|ekit_)") {
        # Require an authenticated WordPress cookie
        if ($http_cookie !~* "wordpress_logged_in_") {
            return 403;
        }
    }
    include fastcgi_params;
    fastcgi_pass php-upstream;
}

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.