Vulnerability in wger (CVE-2026-27838)
Summary
Vulnerability in wger (CVE-2026-27838). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/v2/routine/{pk}/date-sequence-display/.
Original description
The description as published by the source.
wger is a free, open-source workout and fitness manager. Five routine detail action endpoints check a cache before calling self.get_object(). In versions up to and including 2.4, ache keys are scoped only by pk — no user ID is included. When a victim has previously accessed their routine via the API, an attacker can retrieve the cached response for the same PK without any ownership check. Commit e964328784e2ee2830a1991d69fadbce86ac9fbf contains a patch for the issue.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-27838 has been found in wger.
Attackers can target a specific entry point like GET /api/v2/routine/{pk}/date-sequence-display/ over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "wger CVE-2026-27838" on the vendor's site.
CVE-2026-27838 (wger) — CWE-639
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v2/routine/{pk}/date-sequence-display/ / GET /api/v2/routine/{pk}/date-sequence-gym/ / GET /api/v2/routine/{pk}/structure/ / GET /api/v2/routine/{pk}/logs/
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.
A vulnerability (CWE-639) exists in wger. Attackers reach the vulnerable code path via GET /api/v2/routine/{pk}/date-sequence-display/.
Check the vendor advisory for the affected versions of wger. Attack surface: GET /api/v2/routine/{pk}/date-sequence-display/ / GET /api/v2/routine/{pk}/date-sequence-gym/ / GET /api/v2/routine/{pk}/structure/ / GET /api/v2/routine/{pk}/logs/.
Severity: ?. 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 GET /api/v2/routine/{pk}/date-sequence-display/ 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/{pk}/date-sequence-display/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v2/routine/{pk}/date-sequence-display/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /api/v2/routine/{pk}/date-sequence-display/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com