Vulnerabilities > Litespeedtech > Litespeed Cache
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2024-10-20 | CVE-2024-44000 | Insufficiently Protected Credentials vulnerability in Litespeedtech Litespeed Cache Insufficiently Protected Credentials vulnerability in LiteSpeed Technologies LiteSpeed Cache allows Authentication Bypass.This issue affects LiteSpeed Cache: from n/a before 6.5.0.1. | 9.8 |
2024-07-24 | CVE-2024-3246 | Cross-Site Request Forgery (CSRF) vulnerability in Litespeedtech Litespeed Cache The LiteSpeed Cache plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 6.2.0.1. | 5.4 |
2024-01-11 | CVE-2023-4372 | Cross-site Scripting vulnerability in Litespeedtech Litespeed Cache The LiteSpeed Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'esi' shortcode in versions up to, and including, 5.6 due to insufficient input sanitization and output escaping on user supplied attributes. | 5.4 |
2023-05-25 | CVE-2022-46800 | Cross-Site Request Forgery (CSRF) vulnerability in Litespeedtech Litespeed Cache Cross-Site Request Forgery (CSRF) vulnerability in LiteSpeed Technologies LiteSpeed Cache plugin <= 5.3 versions. | 8.8 |
2022-01-03 | CVE-2021-24963 | Cross-site Scripting vulnerability in Litespeedtech Litespeed Cache The LiteSpeed Cache WordPress plugin before 4.4.4 does not escape the qc_res parameter before outputting it back in the JS code of an admin page, leading to a Reflected Cross-Site Scripting | 3.5 |
2022-01-03 | CVE-2021-24964 | Cross-site Scripting vulnerability in Litespeedtech Litespeed Cache The LiteSpeed Cache WordPress plugin before 4.4.4 does not properly verify that requests are coming from QUIC.cloud servers, allowing attackers to make requests to certain endpoints by using a specific X-Forwarded-For header value. | 2.6 |
2020-12-26 | CVE-2020-29172 | Cross-site Scripting vulnerability in Litespeedtech Litespeed Cache A cross-site scripting (XSS) vulnerability in the LiteSpeed Cache plugin before 3.6.1 for WordPress can be exploited via the Server IP setting. | 4.3 |