# CVE-2026-116763: The LiteSpeed Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-wgrw-7pq3-7r4q

## What is CVE-2026-116763?

CVE-2026-116763 is a medium-severity vulnerability in litespeedtech LiteSpeed Cache, published on 29 Oct 2026. 

### Official description

The LiteSpeed Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 7.9.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This vulnerability is only exploitable when the HTML Minify option (O_OPTM_HTML_MIN) is enabled and a companion plugin renders stored comment content into a raw-text context such as a JSON-LD script block on the same page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-116763?


## How do I fix CVE-2026-116763?

No fix has been published for CVE-2026-116763 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116763 being exploited?

There is no known exploitation of CVE-2026-116763 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116763 and fix it if it is affected.

What it is: CVE-2026-116763 is a medium-severity vulnerability in litespeedtech LiteSpeed Cache, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116763 in the wild and no public exploit code.

Affected product: litespeedtech LiteSpeed Cache. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116763/ (Markdown: https://insights.sbomify.com/CVE-2026-116763/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116763
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116763
- OSV: https://osv.dev/vulnerability/CVE-2026-116763

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116763/
Summaries are generated and may contain mistakes; the official description above is the record.