CSRF in Wger-Project Wger
CVE-2026-45161
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.
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.4 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Wger-Project Wger — versions < 2.6
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-45161?
- CVE-2026-45161 is a medium-severity vulnerability in Wger-Project Wger, classified under Cross-Site Request Forgery (CSRF). CVSS score: 5.4/10. Published 2026-10-07.
- How severe is CVE-2026-45161?
- Medium severity. CVSS v3 base score is 5.4 out of 10.