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)
Product
te-st leyka vulnerabilities
5 published CVES affecting te-st leyka, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 0
- High
- 0
- Medium
- 5
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest te-st leyka CVEs
Newest publication first
-
MediumCVSS 4.8 EPSS 0.45%
-
CVE-2023-4917 Leyka <= 3.30.7 - Authenticated (Subscriber+) Sensitive Information Exposure
PublishedMediumCVSS 6.5 EPSS 0.75%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 i...
-
CVE-2023-33325 WordPress Leyka Plugin <= 3.30.1 is vulnerable to Cross Site Scripting (XSS)
PublishedMediumCVSS 6.1 EPSS 0.38%Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Teplitsa of social technologies Leyka plugin <= 3.30.1 versions.
-
CVE-2023-39314 WordPress Leyka Plugin <= 3.30.2 is vulnerable to Cross Site Scripting (XSS)
PublishedMediumCVSS 6.1 EPSS 0.39%Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Teplitsa of social technologies Leyka plugin <= 3.30.2 versions.
-
CVE-2023-27450 WordPress Leyka Plugin <= 3.29.2 is vulnerable to Cross Site Scripting (XSS)
PublishedMediumCVSS 6.1 EPSS 0.38%Unauth. Stored Cross-Site Scripting (XSS) vulnerability in Teplitsa of social technologies Leyka plugin <= 3.29.2 versions.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.