Leyka
leyka · plugin
Known security vulnerabilities for Leyka. Find out in seconds which version runs on your site with WP Lens.
12 known vulnerabilities
7 exploitable without logging in · latest Aug 20, 2026
Closed on wordpress.org
Removed from the directory on Sep 11, 2026 · reason: no reason given. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 8.8
CVE-2023-27442unauthenticated · needs a click≤ 3.29.2
WordPress Leyka Plugin <= 3.29.2 is vulnerable to Cross Site Request Forgery (CSRF)
- High 8.8
CVE-2023-33327login required≤ 3.30.2
WordPress Leyka plugin <= 3.30.2 - Privilege Escalation vulnerability
- High 7.6
CVE-2026-66677login required≤ 3.32.3
WordPress Leyka plugin <= 3.32.3 - Broken Authentication vulnerability
- High 7.5
CVE-2025-52805unauthenticated · needs a click≤ 3.32.1
WordPress Leyka plugin <= 3.32.1 - Local File Inclusion vulnerability
- Medium 6.5
CVE-2025-53275login required≤ 3.32.1
WordPress Leyka plugin <= 3.32.1 - Cross Site Scripting (XSS) vulnerability
- Medium 6.5
CVE-2025-26766login required≤ 3.31.8
WordPress Leyka plugin <= 3.31.8 - Cross Site Scripting (XSS) vulnerability
- Medium 6.5
CVE-2023-4917subscriber+≤ 3.30.7
Leyka <= 3.30.7 - Authenticated (Subscriber+) Sensitive Information Exposure
- Medium 6.1
CVE-2023-33325unauthenticated · needs a click≤ 3.30.1
WordPress Leyka Plugin <= 3.30.1 is vulnerable to Cross Site Scripting (XSS)
- Medium 6.1
CVE-2023-39314unauthenticated · needs a click≤ 3.30.2
WordPress Leyka Plugin <= 3.30.2 is vulnerable to Cross Site Scripting (XSS)
- Medium 6.1
CVE-2023-27450unauthenticated · needs a click≤ <= 3.29.2
WordPress Leyka Plugin <= 3.29.2 is vulnerable to Cross Site Scripting (XSS)
- Medium 5.3
CVE-2024-49252unauthenticated≤ 3.31.6
WordPress leyka plugin <=3.31.6 - Broken Access Control vulnerability
- Medium 5.3
CVE-2024-35683unauthenticated≤ 3.31.1
WordPress Leyka plugin <= 3.31.1 - Broken Access Control vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).