# CVE-2025-71177: LavaLite CMS <= 10.1.0 Stored XSS via Package Creation and Search

> Authenticated users can inject malicious scripts via package fields, leading to session hijacking and credential theft for other users viewing search results.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Jan 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-w7rq-fgx4-4xcm

## What is CVE-2025-71177?

CVE-2025-71177 is a medium-severity cross-site scripting vulnerability in LavaLite CMS, published on 23 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

LavaLite CMS versions up to and including 10.1.0 contain a stored cross-site scripting vulnerability in the package creation and search functionality. Authenticated users can supply crafted HTML or JavaScript in the package Name or Description fields that is stored and later rendered without proper output encoding in package search results. When other users view search results that include the malicious package, the injected script executes in their browsers, potentially enabling session hijacking, credential theft, and unauthorized actions in the context of the victim.

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

## Which versions are affected by CVE-2025-71177?

2 open source packages ship an affected version, including lavalite/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lavalite/cms` | Packagist | All versions to 10.1.0 | None |
| `lavalite/cms` | Packagist | All versions to 10.1.0 | None |

Products: Lavalite Lavalite.

## How do I fix CVE-2025-71177?

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

## Is CVE-2025-71177 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-71177 exists.

## Other vulnerabilities in LavaLite CMS

- [CVE-2023-27238](https://insights.sbomify.com/CVE-2023-27238/): LavaLite vulnerable to web cache poisoning (critical 9.8)
- [CVE-2025-70866](https://insights.sbomify.com/CVE-2025-70866/): Auth bypass in n/a (high 8.8)
- [CVE-2023-36983](https://insights.sbomify.com/CVE-2023-36983/): Information disclosure in n/a (high 7.5)
- [CVE-2023-36984](https://insights.sbomify.com/CVE-2023-36984/): Information disclosure in n/a (high 7.5)
- [CVE-2022-42188](https://insights.sbomify.com/CVE-2022-42188/): Lavalite vulnerable to Arbitrary File Read via Directory Traversal (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-71177 and fix it if it is affected.

What it is: CVE-2025-71177 is a medium-severity cross-site scripting vulnerability in LavaLite CMS, published on 23 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-71177 exists.

Affected packages and fixed versions:
- lavalite/cms (Packagist): affected all versions up to 10.1.0; no fix listed
- lavalite/cms (Packagist): affected all versions up to 10.1.0; no fix listed

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-2025-71177/ (Markdown: https://insights.sbomify.com/CVE-2025-71177/index.md)
```

## Sources

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

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