Categories
CVE-2026-43978 high CVSS 8.1

Privilege Escalation in wger (CVE-2026-43978)

Summary

Vulnerability in wger (CVE-2026-43978). Confidential information can be exposed externally. Exploitable via trainer.identity.

Original description

The description as published by the source.

wger is a free, open-source workout and fitness manager. In versions prior to 2.6, a gym trainer can escalate their session to any higher-privileged account (gym manager, general manager) by chaining two calls to the trainer-login endpoint. Once a trainer performs a legitimate switch into a low-privileged user, the session flag trainer.identity is set and this flag alone bypasses the permission check on all subsequent trainer-login calls. This grants full gym administration capabilities including viewing all member data, modifying contracts, managing gym configuration, and accessing other trainers' and managers' personal information. This issue has been fixed in version 2.6.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-43978 has been found in wger.
Attackers can target a specific entry point like trainer.identity over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "wger CVE-2026-43978" on the vendor's site.

CVE-2026-43978 (wger) — CWE-269 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: trainer.identity / request.user / gym_trainer
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-269) exists in wger. Attackers reach the vulnerable code path via trainer.identity.

📍 Affected scope

Check the vendor advisory for the affected versions of wger. Attack surface: trainer.identity / request.user / gym_trainer.

🔥 Severity

Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'wger' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'wger' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で wger を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip wger
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
PyPI wger
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.5"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details