# CVE-2025-8795: LitmusChaos Litmus login access control

> Attackers can bypass access controls in the Litmus login endpoint to gain unauthorized privileges or access data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2025
- **Updated:** 13 Aug 2025
- **Also known as:** GHSA-qqx5-rxfw-q347

## What is CVE-2025-8795?

CVE-2025-8795 is a medium-severity missing authorization vulnerability in LitmusChaos Litmus, published on 10 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in LitmusChaos Litmus up to 3.19.0. This affects an unknown part of the file /auth/login. The manipulation of the argument projectID leads to improper access controls. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


Products: Litmuschaos Litmus.

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

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

## Is CVE-2025-8795 being exploited?

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

## Other vulnerabilities in LitmusChaos Litmus

- [CVE-2025-8791](https://insights.sbomify.com/CVE-2025-8791/): LitmusChaos Litmus list_projects improper authorization (medium 5.3)
- [CVE-2025-8792](https://insights.sbomify.com/CVE-2025-8792/): LitmusChaos Litmus client-side enforcement of server-side security (medium 5.3)
- [CVE-2025-8793](https://insights.sbomify.com/CVE-2025-8793/): LitmusChaos Litmus resource injection (medium 5.3)
- [CVE-2025-8796](https://insights.sbomify.com/CVE-2025-8796/): LitmusChaos Litmus Delete Request delete_project authorization (medium 5.3)
- [CVE-2025-8797](https://insights.sbomify.com/CVE-2025-8797/): LitmusChaos Litmus LocalStorage permission (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8795 is a medium-severity missing authorization vulnerability in LitmusChaos Litmus, published on 10 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8795 exists.

Affected product: LitmusChaos Litmus. 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-2025-8795/ (Markdown: https://insights.sbomify.com/CVE-2025-8795/index.md)
```

## Sources

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

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