Vikunja 是一个开源的自托管任务管理平台。在版本 2.3.0 至 2.4.0 期间,拥有共享子项目“写入(Write)”权限但不具备“管理员(Admin)”权限的用户,可以通过向 提交 来将该子项目从其父级层级中分离出去。 中的 授权检查以及 中的 逻辑,仅对非零的父级 ID 值进行门控(即仅当 非零时才要求 Admin 权限),而 总是会将 持久化保存。因此,显式传入零值可以绕过为修复 CVE-2026-35595 而引入的 Admin 权限要求。 这种分离操作会切断递归的权限继承链,并可能干扰项目所有者的
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| go-vikunja | vikunja | >= 2.3.0, < 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.3.0, < 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-55066 | 7.1 HIGH | Vikunja: Cross-tenant IDOR in kanban move-task endpoint via unauthorized body task_id |
| 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 |
No comments yet