Vikunja 是一个开源的自托管任务管理平台。在 2.4.0 版本之前, 接口接受请求体中提供的 ,但 中的 方法仅对 URL 中的项目、视图和桶进行权限验证。随后, 调用 时并未对任务本身进行额外的权限检查,从而返回了目标任务的内容;当攻击者选择一个“已完成”桶时,还可以修改任务的完成状态。由于任务标识符是全局顺序值,经过认证的用户可以枚举跨租户的任务,并通过共用该模型的 v1 和 v2 路由修改这些任务的完成元数据。该问题已在 2.4.0 版本中修复。
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| go-vikunja | vikunja | < 2.4.0 |
affected |
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| go-vikunja | vikunja | < 2.4.0 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-55065 | 8.1 HIGH | Vikunja: Improper Authorization and Authorization Bypass Through User-Controlled Key in co |
| CVE-2026-54766 | 5.3 MEDIUM | Vikunja: Project duplication bypasses write-permission check on the target parent project |
| CVE-2026-55067 | 5.0 MEDIUM | Vikunja: Authenticated cross-tenant kanban-bucket relocation via `project_view_id` mass-as |
| CVE-2026-55064 | 4.3 MEDIUM | Vikunja incomplete fix for CVE-2026-35595: Write-only user can detach shared project from |
No comments yet