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 `` 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.
CVE-2026-45161
MEDIUMPre-NVD 5.45.4Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.4 from GitHub Security Advisory published 2026-10-07. A secondary CVSS source baseline 5.4; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 5.4Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 5.4
- EG Score
- 5.4MEDIUMhigh confidence
- EG Risk
- 24EG Risk 24/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity54% × 45%The EG Score, 5.4 of 10.Exploitation<0.1% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- <0.1%
- EPSS %ILE
- below the 1st
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 7, 2026
Last Modified
October 7, 2026
Advisory Details (2)
Auto-updated Oct 7, 2026Patch available. Sources: github, github_release.
GitHub release Patch Available
2.6
Patch available: wger-project/wger 2.6
https://github.com/wger-project/wger/releases/tag/2.6GitHub advisoryMentions a patch (unverified)
wger: trainer_login accepts GET - CSRF bypass enables forced session rebinding · Advisory · wger-project/wger · GitHub
https://github.com/wger-project/wger/security/advisories/GHSA-xf64-4pmc-h8qfVendor Advisories for CVE-2026-45161(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | wger | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| wger | 1.1 ... 2.1 (14 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 24× in last 7d / 24× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-12 16:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-10-12 16:04 UTCEG score recompute
- 2026-10-11 23:38 UTCGHSA enrichmentGHSA-xf64-4pmc-h8qf · GitHub CVSS 5.4
- 2026-10-11 19:46 UTCEG score recompute
- 2026-10-11 17:01 UTCEG score recompute
- 2026-10-11 14:26 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-10-10 22:16 UTCEG score recompute
- 2026-10-10 22:16 UTCGHSA enrichmentGHSA-xf64-4pmc-h8qf · GitHub CVSS 5.4
- 2026-10-10 20:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-10-09 20:55 UTCEG score recompute
- 2026-10-09 20:55 UTCGHSA enrichmentGHSA-xf64-4pmc-h8qf · GitHub CVSS 5.4
- 2026-10-09 20:07 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-10-08 19:35 UTCEG score recompute
- 2026-10-08 19:35 UTCGHSA enrichmentGHSA-xf64-4pmc-h8qf · GitHub CVSS 5.4
- 2026-10-08 17:12 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-10-07 17:20 UTCEG score recompute
- 2026-10-07 17:19 UTCGHSA enrichmentGHSA-xf64-4pmc-h8qf · GitHub CVSS 5.4
- 2026-10-07 14:48 UTCGHSA enrichmentGHSA-xf64-4pmc-h8qf · GitHub CVSS 5.4
- 2026-10-07 14:28 UTCEG score recompute
- 2026-10-07 14:27 UTCGHSA enrichmentGHSA-xf64-4pmc-h8qf · GitHub CVSS 5.4
- 2026-10-07 13:52 UTCEG score recomputeFirst assessed: 5.4 MEDIUM
- 2026-10-07 13:51 UTCGHSA enrichmentGHSA-xf64-4pmc-h8qf · GitHub CVSS 5.4
- 2026-10-07 13:51 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:wger
Frequently asked(5)
What is CVE-2026-45161?
CVE-2026-45161 is a medium-severity vulnerability; its CVE record was published on October 7, 2026. wger is a free, open-source workout and fitness manager. Prior to version 2.6, the trainerlogin view in wger accepts GET requests and executes djangologin() without any CSRF protection, because Django's CsrfViewMiddleware only enforces tokens on unsafe methods (POST/PUT/PATCH/DELETE). An attacker…
When was the CVE record for CVE-2026-45161 published?
The CVE record for CVE-2026-45161 was published on October 7, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 7, 2026; the record at its source may have been updated since.
Is CVE-2026-45161 actively exploited?
CVE-2026-45161 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45161?
CVE-2026-45161 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-45161?
A fix for CVE-2026-45161 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45161 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45161
Is Your Infrastructure Affected by CVE-2026-45161?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.