Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55065 high CVSS 8.1

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

Summary

Vulnerability in code.vikunja.io/api (CVE-2026-55065). Data can be tampered with by attackers. Exploitable via GET /api/v1/projects/. Mitigation: upgrade to 2.4.0 or later.

Original description

The description as published by the source.

Summary

A user with only a single self-owned project can permanently destroy the Kanban bucket assignments (task_buckets) and task ordering (task_positions) of any other project view in the entire instance. The ProjectView.Delete model method runs three SQL statements: the first is properly scoped to (view_id, project_id), but the next two cascading deletes on task_buckets and task_positions filter only on the URL-supplied project_view_id. The permission check (CanDelete) gates on Admin of the URL :project but never confirms that the URL :view actually belongs to that project.

Details

ProjectView.Delete (file: pkg/models/project_view.go, line 250) cascades on the bare pv.ID for the second and third deletes, ignoring pv.ProjectID:

func (pv *ProjectView) Delete(s *xorm.Session, _ web.Auth) (err error) {
    _, err = s.
        Where("id = ? AND project_id = ?", pv.ID, pv.ProjectID).   // (a) scoped — OK
        Delete(&ProjectView{})
    if err != nil {
        return
    }

    _, err = s.Where("project_view_id = ?", pv.ID).Delete(&TaskBucket{})    // (b) UNSCOPED
    if err != nil {
        return
    }

    _, err = s.Where("project_view_id = ?", pv.ID).Delete(&TaskPosition{})  // (c) UNSCOPED
    return
}

pv.ID and pv.ProjectID come straight from the URL path via c.Bind — see the param tags on the struct (pkg/models/project_view.go, lines 133–137):

type ProjectView struct {
    ID        int64 `xorm:"auto…

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-55065 has been found in code.vikunja.io/api.
Attackers can target a specific entry point like GET /api/v1/projects/ over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.1/10.
What to do: upgrade code.vikunja.io/api to 2.4.0 or later.
If unsure, ask your IT team or search "code.vikunja.io/api CVE-2026-55065" on the vendor's site.

CVE-2026-55065 (code.vikunja.io/api) — CWE-285 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/projects/ / PUT /api/v1/projects / DELETE /api/v1/projects/P_A/views/V / DELETE /api/v1/projects/{attacker_pid}/views/{victim_vid}
Patched: 2.4.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-285) exists in code.vikunja.io/api. Attackers reach the vulnerable code path via GET /api/v1/projects/.

📍 Affected scope

Check the vendor advisory for the affected versions of code.vikunja.io/api. Attack surface: GET /api/v1/projects/ / PUT /api/v1/projects / DELETE /api/v1/projects/P_A/views/V / DELETE /api/v1/projects/{attacker_pid}/views/{victim_vid}.

🔥 Severity

Severity: High (CVSS 8.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 2.4.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/projects/ 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/projects/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

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

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

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

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

Affected packages

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

References

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