← Back
CVE-2026-43948
critical
CVSS 9.9
Authorization Flaw in wger (CVE-2026-43948)
Summary
vulnerability in wger (CVE-2026-43948). Successful exploitation can lead to full system takeover. Exploitable via `GET /en/gym/user/`. Mitigation: upgrade to `2.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-43948** has been found in wger.
Attackers can target a specific entry point like `GET /en/gym/user/` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade wger to **2.6** or later.
If unsure, ask your IT team or search "wger CVE-2026-43948" on the vendor's site.
CVE-2026-43948 (wger) — CWE-863 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /en/gym/user/ / POST /en/user/login / GET /en/gym/user/2/reset-user-password / `reset_user_password`
Patched: `2.6` — apply immediately
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
**incorrect authorization** (CWE-863) exists in wger. Attackers reach the vulnerable code path via `GET /en/gym/user/` without authentication.
📍 Affected scope
wger — . Attack surface: GET /en/gym/user/ / POST /en/user/login / GET /en/gym/user/2/reset-user-password / `reset_user_password`.
🔥 Severity
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.6**.
🛡️ 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 `GET /en/gym/user/` 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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /en/gym/user/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /en/gym/user/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade wger to 2.6ステージング環境で 2.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /en/gym/user/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
wger
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6"}]}]