Leyka <= 3.30.2 - Privilege Escalation via Admin Password Reset
Strategic Overview
- Status
- Patched in 3.30.3
- Affected Plugin
- Leyka
- Affected Version
<= 3.30.2- CVSS
- 9.8Critical
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2023-33327
At a glance
CVE-2023-33327 is a critical-severity Authorization Bypass Through User-Controlled Key vulnerability in the Leyka WordPress plugin, affecting versions <= 3.30.2. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.30.3; sites on affected versions should update now. Disclosed May 2023, reported by Nguyen Anh Tien.
Vulnerability Overview
The Leyka plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 3.30.2. This allows donors users to gain administrator access by setting the passwords for an administrator account when initially setting their password.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Leyka <= 3.30.2 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 Leyka the fix is 3.30.3: builds <= 3.30.2 are affected, anything from 3.30.3 onward is not.
Remediation
Update to version 3.30.3, 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: Leyka 3.30.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Leyka
- 8.1CVE-2025-52805: Leyka <= 3.31.9 Local File Inclusion
CVE-2025-52805 - 7.2CVE-2023-27450: Leyka <= 3.29.2 Stored Cross-Site Scripting
CVE-2023-27450 - 6.4CVE-2025-53275: Leyka <= 3.31.9 Stored Cross-Site Scripting
CVE-2025-53275 - 6.4CVE-2025-26766: Leyka <= 3.31.8 Stored Cross-Site Scripting
CVE-2025-26766 - 6.1CVE-2023-39314: Leyka <= 3.30.2 Reflected Cross-Site Scripting
CVE-2023-39314 - 6.1CVE-2023-33325: Leyka <= 3.30.1 Reflected Cross-Site Scripting
CVE-2023-33325 - 5.4CVE-2023-27442: Leyka <= 3.29.2 Cross-Site Request Forgery
CVE-2023-27442 - 5.3CVE-2024-35683: Leyka <= 3.31.1 Missing Authorization
CVE-2024-35683
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C