CVE-2026-45161

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account, but needs a user to act. Limited direct impact.

Exploit odds

0.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-10-07 14:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-07 17:16 UTC Last updatedMost recent change to the record

Details

Published

2026-10-07 14:17 UTC

Last modified

2026-10-07 17:16 UTC

Exploit probability

0.1% · EPSS, next 30 days

Weakness

CWE-352 · Cross-site request forgery

Record status

Deferred

Attack profile CVSS 3.1 · 5.4

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None