Skip to main content
VulnerabilityPublished

CVE-2026-45161: wger · Cross-Site Request Forgery (CSRF)

Affects wgerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 2.6 when convenient.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade wger and wger-project/wger to 2.6.

Affected software

ProductAffectedFixed in
wger-projectwgerAffected
  • <2.6
Fixed in
  • 2.6
GitHubwger-project/wgerpkg:github/wger-project/wgerOther threatsAffected
  • <2.6
Fixed in
  • 2.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade wger to version 2.6 or later, where this CSRF vulnerability has been fixed by disallowing unsafe GET requests for the `trainer_login` view or adding proper CSRF protections. No other mitigations are indicated or necessary once the upgrade is applied.

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.

References

Community reviews

Loading reviews…