CVE-2025-0968

ElementsKit Elementor addons <= 3.4.0 - Unauthenticated Information Exposure via get_megamenu_content Function

2025-02-18 22:37
stealthcopter

Strategic Overview

Status
Patched in 3.4.1
Affected Version
<= 3.4.0
CVSS
5.3Medium
Weakness type
CWE-284 · Improper Access Control
CVE
CVE-2025-0968
View all ElementsKit Elementor Addons – Advanced Widgets & Templates Addons for Elementor vulnerabilities

At a glance

CVE-2025-0968 is a medium-severity Improper Access Control vulnerability in the ElementsKit Elementor Addons WordPress plugin, affecting versions <= 3.4.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.4.1; sites on affected versions should update now. Disclosed February 2025, reported by stealthcopter.

Vulnerability Overview

The ElementsKit Elementor addons plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.4.0 due to a missing capability checks on the get_megamenu_content() function. This makes it possible for unauthenticated attackers to view any item created in Elementor, such as posts, pages and templates including drafts, trashed 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-284: Improper Access Control

ElementsKit Elementor Addons <= 3.4.0 carries this weakness at get_megamenu_content(), and reaching it takes no account at all. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.

Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For ElementsKit Elementor Addons the fix is 3.4.1: builds <= 3.4.0 are affected, anything from 3.4.1 onward is not.

Remediation

Update to version 3.4.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.4.1 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