# CVE-2026-125369: Bitpoll through 0.11.0 Unauthenticated Vote and Comment Disclosure via Unscoped Lookups


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-frxv-g6p8-4jv8

## What is CVE-2026-125369?

CVE-2026-125369 is a medium-severity vulnerability in fsinfuhh Bitpoll, published on 9 Nov 2026. 

### Official description

Bitpoll through 0.11.0 contains an insecure direct object reference vulnerability that allows unauthenticated attackers to read votes and comments from other polls via unscoped object lookups in views.py. Attackers can pair any public poll slug with sequential vote or comment IDs in vote, vote_delete, vote_assign, or delete_comment GET requests to read names and comments from restricted polls.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-125369 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125369 is a medium-severity vulnerability in fsinfuhh Bitpoll, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125369 in the wild and no public exploit code.

Affected product: fsinfuhh Bitpoll. 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-125369/ (Markdown: https://insights.sbomify.com/CVE-2026-125369/index.md)
```

## Sources

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

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