Authentication Bypass in wger (CVE-2026-46437)
Summary
Authentication bypass in wger (CVE-2026-46437). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/v2/token.
Original description
The description as published by the source.
Summary
A vulnerability exists in the authentication/session lifecycle of wger where bearer-style API credentials remain valid after a user logs out and after a user changes their password. An attacker who steals a victim’s DRF authtoken (Authorization: Token ...) or JWT refresh token can continue to access protected /api/v2/* endpoints until the token is manually rotated/deleted (DRF token) or naturally expires (JWT refresh).
lifecycle events do not revoke these credentials:
- Logout (
/user/logout) only clears the Django session cookie viadjango_logout()and does not revoke API tokens. - Password change updates the password hash, but does not revoke:
- existing DRF tokens stored in
authtoken_token - existing JWT refresh tokens (no server-side revocation list or token versioning); refresh can continue minting new access tokens until refresh expiry.
- existing DRF tokens stored in
Vulnerable Files
wger/wger/core/views/user.py(logout implementation)wger/settings/settings_global.py(DRF auth configuration, SimpleJWT defaults)wger/settings/main.py(commonly used production defaults for JWT lifetimes)wger/wger/utils/api_token.py(authtoken rotation is manual only)
PoC (Proof of Concept)
Manual Exploitation Steps
- Create a user account.
- Obtain a JWT refresh token:
POST /api/v2/tokenwith username/password.
- Obtain a DRF token (API key):
- use
/user/api-key(or create token via admin/DB in a test environment).
4…
- use
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-46437 has been found in wger.
Attackers can target a specific entry point like POST /api/v2/token over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "wger CVE-2026-46437" on the vendor's site.
CVE-2026-46437 (wger) — CWE-287 / CVSS v3 4.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/v2/token / POST /api/v2/token/refresh / wger / authtoken_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.
Authentication bypass (CWE-287) exists in wger. Attackers reach the vulnerable code path via POST /api/v2/token without authentication.
Check the vendor advisory for the affected versions of wger. Attack surface: POST /api/v2/token / POST /api/v2/token/refresh / wger / authtoken_token.
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure.
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 POST /api/v2/token 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 'POST /api/v2/token' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v2/tokenへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /api/v2/token on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- package pypi.org
- web github.com
- web github.com