Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-91982 medium CVSS 4.3

Vulnerability in code.vikunja.io/api (CVE-2026-91982)

Summary

Vulnerability in code.vikunja.io/api (CVE-2026-91982). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/v1/user/settings/totp. Mitigation: upgrade to 2.6.0 or later.

Original description

The description as published by the source.

Summary

Once a user has TOTP enabled, the API still hands back the raw shared secret to anyone holding that account's access token. Reading it doesn't ask for the password, even though disabling TOTP does. So a stolen token, an XSS, or a browser left open is enough to copy the second factor into your own authenticator and keep generating valid codes indefinitely.

Details

GET /api/v1/user/settings/totp returns the full TOTP object, including the secret field and the otpauth:// provisioning URL. GET /api/v1/user/settings/totp/qrcode renders the same secret as a QR image. Neither requires re-authentication, the access token alone is enough.

This is inconsistent with the rest of the flow: POST /api/v1/user/settings/totp/disable calls CheckUserPassword before it will turn TOTP off. So the destructive action is gated behind the password, but reading out the secret that backs the second factor isn't. There's also no reason for the secret to be readable at all once enrollment is finished, the client only needs it during setup.

The fix is to stop returning secret/url/the QR code once enabled is true (only expose them during the enrollment window). Requiring the password on the read, like disable already does, would also be reasonable.

PoC

The attacker needs the victim's access token, from an XSS, a leaked/stolen token, or an unlocked session. TOTP must already be enabled on the account.

  1. With the victim's bearer token, call:
GET /api/v1/user/settings/totp…

Source: NIST National Vulnerability Database 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-91982 has been found in code.vikunja.io/api.
Attackers can target a specific entry point like GET /api/v1/user/settings/totp over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade code.vikunja.io/api to 2.6.0 or later.
If unsure, ask your IT team or search "code.vikunja.io/api CVE-2026-91982" on the vendor's site.

CVE-2026-91982 (code.vikunja.io/api) — CWE-312 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/user/settings/totp / GET /api/v1/user/settings/totp/qrcode / POST /api/v1/user/settings/totp/disable
Patched: 2.6.0 — 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

A vulnerability (CWE-312) exists in code.vikunja.io/api. Attackers reach the vulnerable code path via GET /api/v1/user/settings/totp.

📍 Affected scope

Check the vendor advisory for the affected versions of code.vikunja.io/api. Attack surface: GET /api/v1/user/settings/totp / GET /api/v1/user/settings/totp/qrcode / POST /api/v1/user/settings/totp/disable.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.6.0.

🛡️ 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 /api/v1/user/settings/totp requests with malformed payloads or SQL meta-characters. Run grep -r 'code.vikunja.io/api' . 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 'code.vikunja.io/api' . | grep -v node_modules

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

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /api/v1/user/settings/totp' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/v1/user/settings/totp への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade code.vikunja.io/api to 2.6.0

    ステージング環境で 2.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /api/v1/user/settings/totp on staging to confirm patch closes the vector

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

Affected packages

go code.vikunja.io/api
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.6.0"}]}]

References

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