LiteSpeed Cache

An unauthenticated attacker must supply a validly signed esi query value while placing a separate malicious esi value in the POST body. With PHP's default request-merge order, the POST value wins at execution even though the query value was validated. Reflected script execution also requires victim interaction. The export does not explain how the attacker obtains the valid signed value; it does not establish signature forgery. Authoritative affected range: <= 7.9. Confirmed remediation: 7.9.1.

LiteSpeed Cache through 7.9 allows an unauthenticated requester to influence a server-side request. The request can reach network resources available to the WordPress host and can expose or alter data returned through the affected flow.

LiteSpeed Cache through 7.7 uses a flawed regular expression to remove width and height from img tags when Lazy Load Images and Add Missing Sizes are enabled. An Author can craft image attributes that become stored script and execute when a visitor opens the post.

LiteSpeed Cache through 7.8.1 processes crafted decimal character references inside an allowed code element into a malicious data-settings attribute. On sites where previously approved commenters can post again and require_name_email is disabled, an unauthenticated commenter can store script that executes for page visitors.

An unauthenticated attacker who can bypass the IP-based QUIC.cloud callback validation under certain reverse-proxy, load-balancer or CDN configurations can submit CSS content to /wp-json/litespeed/v1/notify_ccss or /wp-json/litespeed/v1/notify_ucss. The endpoints save the content to disk without sanitization, and later frontend loads render it inline without output escaping. Injected JavaScript executes in the site's origin when that output is viewed. The exact bypass configuration is unspecified; ordinary unauthenticated access is not enough by itself. Affected versions: <= 7.7. Confirmed fixed release: 7.8, based on the official change filtering HTML tags when saving CSS content.

LiteSpeed Cache is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

LiteSpeed Cache is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

LiteSpeed Cache is affected by server-side request forgery. Exposure depends on how the affected operation is made reachable by the site. The vulnerable server can be induced to make attacker-selected network requests.

LiteSpeed Cache is affected by privilege escalation or authentication bypass. Exposure depends on how the affected operation is made reachable by the site. A successful request can grant permissions or access that the caller should not possess.

LiteSpeed Cache is affected by privilege escalation or authentication bypass. Exposure depends on how the affected operation is made reachable by the site. A successful request can grant permissions or access that the caller should not possess.

LiteSpeed Cache is affected by filesystem traversal. Exposure depends on how the affected operation is made reachable by the site. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.

LiteSpeed Cache is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

LiteSpeed Cache is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

LiteSpeed Cache is affected by cross-site scripting. Exploitation requires an authenticated administrator account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

LiteSpeed Cache is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

LiteSpeed Cache is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

LiteSpeed Cache is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

LiteSpeed Cache is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

LiteSpeed Cache is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Litespeed Cache is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

LiteSpeed Cache is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

LiteSpeed Cache is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Litespeed Cache is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.