Information Disclosure in wger (CVE-2026-43977)
Summary
Vulnerability in wger (CVE-2026-43977). Confidential information can be exposed externally. Exploitable via GET /api/v2/routine/.
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, any authenticated user can read another user's private workout session notes, exercise history, and training statistics by calling the /logs/ and /stats/ actions on a routine they do not own. The vulnerability exists in RoutineViewSet (wger/manager/api/views.py). The view defines two custom actions /logs/ and /stats/ that are intended to return data for the requesting user's own training history within a routine. However, the underlying permission check (RoutinePermission.has_object_permission) grants read access to any authenticated user when the routine has is_template=True, regardless of ownership. When the /logs/ or /stats/ actions are invoked against a routine the attacker does not own, they return the owner's private workout history, not the attacker's. 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-43977 has been found in wger.
Attackers can target a specific entry point like GET /api/v2/routine/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "wger CVE-2026-43977" on the vendor's site.
CVE-2026-43977 (wger) — CWE-200 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /api/v2/routine/ / GET /api/v2/routine/{id}/logs/ / GET /api/v2/routine/{id}/stats/ / POST /api/v2/token
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.
Information disclosure (CWE-200) exists in wger. Attackers reach the vulnerable code path via GET /api/v2/routine/ without authentication.
Check the vendor advisory for the affected versions of wger. Attack surface: GET /api/v2/routine/ / GET /api/v2/routine/{id}/logs/ / GET /api/v2/routine/{id}/stats/ / POST /api/v2/token.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/v2/routine/ requests with malformed payloads or SQL meta-characters. 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
-
1Identify exposure identify
grep -r 'wger' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
wgerを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v2/routine/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v2/routine/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /api/v2/routine/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com