# CVE-2026-45161: wger: trainer_login accepts GET - CSRF bypass enables forced session rebinding

> An attacker can force a logged-in trainer to switch sessions to an arbitrary account via a GET request, enabling account takeover.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A: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:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-xf64-4pmc-h8qf, PYSEC-2026-4317

## What is CVE-2026-45161?

CVE-2026-45161 is a medium-severity vulnerability in wger-project wger, published on 7 Oct 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

wger is a free, open-source workout and fitness manager. Prior to version 2.6, the `trainer_login` view in wger accepts GET requests and executes `django_login()` without any CSRF protection, because Django's `CsrfViewMiddleware` only enforces tokens on unsafe methods (POST/PUT/PATCH/DELETE). An attacker can embed a single `<img>` tag on a malicious page; when an authenticated trainer loads that page, their browser auto-issues the GET with the session cookie, forcibly rebinding the trainer's session to an arbitrary user account. Version 2.6 fixes the issue.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

3 open source packages ship an affected version, including wger.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wger` | PyPI | All versions to 2.1 | None |
| `wger` | PyPI | All versions to 2.1 | None |
| `wger` | PyPI | All versions to 2.1 | None |

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

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

## Is CVE-2026-45161 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45161 is a medium-severity vulnerability in wger-project wger, published on 7 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-45161 in the wild and no public exploit code.

Affected packages and fixed versions:
- wger (PyPI): affected all versions up to 2.1; no fix listed
- wger (PyPI): affected all versions up to 2.1; no fix listed
- wger (PyPI): affected all versions up to 2.1; 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-2026-45161/ (Markdown: https://insights.sbomify.com/CVE-2026-45161/index.md)
```

## Sources

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

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