Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55067 medium CVSS 5.0

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

Summary

Vulnerability in code.vikunja.io/api (CVE-2026-55067). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/v1/projects/{project}/views/{view}/buckets/{bucket}. Mitigation: upgrade to 2.4.0 or later.

Original description

The description as published by the source.

Summary

POST /api/v1/projects/{project}/views/{view}/buckets/{bucket} mass-assigns the request body's project_view_id onto the bucket row. The permission check only verifies that the URL-supplied bucket already belongs to the URL-supplied (project, view) pair; the body's project_view_id is never validated. Any signed-in user can therefore take one of their own buckets and graft it into any other tenant's kanban view, with attacker-controlled title and the attacker's account as created_by.

This vulnerability was found using an LLM, and manually verified against latest (2.3.0).

Vulnerable code

pkg/models/kanban.go (lines 348-359):

func (b *Bucket) Update(s *xorm.Session, _ web.Auth) (err error) {
    _, err = s.
        Where("id = ?", b.ID).
        Cols(
            "title",
            "limit",
            "position",
            "project_view_id",   // mass-assigned from the request body
        ).
        Update(b)
    return
}

Bucket.CanUpdate (canDoBucket) only validates that the URL-supplied {bucket} belongs to the URL-supplied {project}/{view}. The body's project_view_id reaches Update unchecked and is written through.

Proof of Concept

Prerequisites: Two registered users (attacker and victim). In the IDs below: attacker's project is 2, kanban view 8; victim's project is 1, kanban view 4.

Step 1: Attacker creates a fresh bucket in their own project.

curl -s -X PUT 'http://localhost:13456/ap…

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-55067 has been found in code.vikunja.io/api.
Attackers can target a specific entry point like POST /api/v1/projects/{project}/views/{view}/buckets/{bucket} over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.0/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-55067" on the vendor's site.

CVE-2026-55067 (code.vikunja.io/api) — CWE-639 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/projects/{project}/views/{view}/buckets/{bucket} / project_view_id / created_by / Bucket.CanUpdate
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-639) exists in code.vikunja.io/api. Attackers reach the vulnerable code path via POST /api/v1/projects/{project}/views/{view}/buckets/{bucket}.

📍 Affected scope

Check the vendor advisory for the affected versions of code.vikunja.io/api. Attack surface: POST /api/v1/projects/{project}/views/{view}/buckets/{bucket} / project_view_id / created_by / Bucket.CanUpdate.

🔥 Severity

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

🔧 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 POST /api/v1/projects/{project}/views/{view}/buckets/{bucket} 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 'POST /api/v1/projects/{project}/views/{view}/buckets/{bucket}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/v1/projects/{project}/views/{view}/buckets/{bucket} への異常なリクエスト (不正な認証ヘッダ・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 POST /api/v1/projects/{project}/views/{view}/buckets/{bucket} 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.4.0"}]}]

References

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