CVE-2026-45161

published 7 Oct 2026 · updated 7 Oct 2026

wger: trainer_login accepts GET - CSRF bypass enables forced session rebinding

5.4MediumCVSS 5.4EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
wger-project<2.6

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-45161 severity on Zeptric[![CVE-2026-45161](https://zeptric.io/badge/cve/CVE-2026-45161.svg)](https://zeptric.io/cve/CVE-2026-45161)