CVE-2025-0661

DethemeKit For Elementor <= 2.1.8 - Authenticated (Contributor+) Protected Post Disclosure

2025-02-12 00:00
Webbernaut

Strategic Overview

Status
Patched in 2.1.9
Affected Plugin
DethemeKit for Elementor
Affected Version
<= 2.1.8
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-0661
View all DethemeKit for Elementor vulnerabilities

At a glance

CVE-2025-0661 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the DethemeKit for Elementor WordPress plugin, affecting versions <= 2.1.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.1.9; sites on affected versions should update now. Disclosed February 2025, reported by Webbernaut.

Vulnerability Overview

The DethemeKit For Elementor plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.36 via the duplicate_post() function due to insufficient restrictions on which posts can be duplicated. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract data from password protected, private, draft, or scheduled posts that they should not have access to by duplicating the post.

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

DethemeKit for Elementor <= 2.1.8 carries this weakness at duplicate_post(), and reaching it takes an account at Contributor level or above. 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 DethemeKit for Elementor the fix is 2.1.9: builds <= 2.1.8 are affected, anything from 2.1.9 onward is not.

Remediation

Update to version 2.1.9, 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: DethemeKit for Elementor 2.1.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-0661https://www.wordfence.com/threat-intel/vulnerabilities/id/1e2c937c-1ff8-4bcc-913b-83bade37d754https://nvd.nist.gov/vuln/detail/CVE-2025-0661

Related records

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