HomeWordPress vulnerabilitiesLeyka
Leyka vulnerabilities
Leyka has 3 known vulnerabilities in this database. The most recent published record is dated 10 Oct 2026.
- Known vulnerabilities
- 3
- Active installs
- Not listed
- Latest version
- Unknown
- Last updated
- Unknown
- Most recent
- 10 Oct 2026
This plugin is shown as closed on WordPress.org, so check the vulnerability record and the developer's current information before deciding whether to keep it installed.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| SQL injection CVE-2026-42717 | High 7.6 | Up to 3.32.3 | No fix: plugin closed | 2 d ago |
| Cross-site scripting (XSS) CVE-2023-2995 | Medium 4.8 | Up to 3.30.3 | No fix: plugin closed | 19 Sep 2023 |
| Sensitive data exposure CVE-2023-4917 | Medium 5.3 | Up to 3.30.3 | No fix: plugin closed | 13 Sep 2023 |
Read the published descriptions
- CVE-2026-42717, 10 Oct 2026
- Administrator SQL Injection in Leyka <= 3.32.3 versions. CVE record
- CVE-2023-2995, 19 Sep 2023
- The Leyka WordPress plugin before 3.30.4 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2023-4917, 13 Sep 2023
- The Leyka plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 3.30.7 via the 'leyka_ajax_get_env_and_options' function. This can allow authenticated attackers with subscriber-level permissions or above to extract sensitive data including Sberbank API key and password, PayPal Client Secret, and more keys and passwords. CVE record
What to do if you run Leyka
If you run Leyka, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Leyka vulnerabilities
Free. We email you when a new vulnerability is published for Leyka, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.