CVE-2024-12059

ElementInvader Addons for Elementor <= 1.3.1 - Missing Authorization to Arbitrary Options Read

2024-12-11 00:00
Francesco Carlucci

Strategic Overview

Status
Patched in 1.3.2
Affected Version
<= 1.3.1
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-12059
View all ElementInvader Addons for Elementor vulnerabilities

At a glance

CVE-2024-12059 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the ElementInvader Addons for Elementor WordPress plugin, affecting versions <= 1.3.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.3.2; sites on affected versions should update now. Disclosed December 2024, reported by Francesco Carlucci.

Vulnerability Overview

The ElementInvader Addons for Elementor plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.3.1 via the eli_option_value shortcode. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract arbitrary options from the wp_options table.

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 interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in ElementInvader Addons for Elementor <= 1.3.1 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For ElementInvader Addons for Elementor the fix is 1.3.2: builds <= 1.3.1 are affected, anything from 1.3.2 onward is not.

Remediation

Update to version 1.3.2, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: ElementInvader Addons for Elementor 1.3.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C