LiteSpeed Cache 漏洞列表
共找到 5 个与 LiteSpeed Cache 相关的漏洞
📅 加载漏洞趋势中...
-
CVE-2024-44000: LiteSpeed Cache <= 6.4.1 - Sensitive Information Exposure POC
The LiteSpeed Cache plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 6.4.1 through the debug.log file that is publicly exposed. This makes it possible for unauthenticated attackers to view potentially sensitive information contained in the exposed log file. The log file may contain user cookies making it possible for an attacker to log in with any session that is actively valid and exposed in the log file. Note: the debug feature must be enabled for this to be a concern and this feature is disabled by default. -
CVE-2023-40000: LiteSpeed Cache <= 5.7 - Unauthenticated Stored XSS POC
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LiteSpeed Technologies LiteSpeed Cache allows Stored XSS.This issue affects LiteSpeed Cache- from n/a through 5.7. -
CVE-2023-40000: LiteSpeed Cache <= 5.7 - Unauthenticated Stored XSS POC
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LiteSpeed Technologies LiteSpeed Cache allows Stored XSS.This issue affects LiteSpeed Cache- from n/a through 5.7. -
CVE-2024-28000: WordPress LiteSpeed Cache - Unauthenticated Privilege Escalation to Admin POC
Incorrect Privilege Assignment vulnerability in LiteSpeed Technologies LiteSpeed Cache litespeed-cache allows Privilege Escalation.This issue affects LiteSpeed Cache: from 1.9 through 6.3.0.1. -
CVE-2024-44000: LiteSpeed Cache <= 6.4.1 - Sensitive Information Exposure POC
The LiteSpeed Cache plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 6.4.1 through the debug.log file that is publicly exposed. This makes it possible for unauthenticated attackers to view potentially sensitive information contained in the exposed log file. The log file may contain user cookies making it possible for an attacker to log in with any session that is actively valid and exposed in the log file. Note: the debug feature must be enabled for this to be a concern and this feature is disabled by default.