Vikunja 2.6.0 之前的版本在将团队关联到项目时未对团队访问权限进行验证,允许已认证用户枚举所有团队及其成员。攻击者可通过项目的团队端点(project teams endpoint)附加任意团队 ID,从而获取未授权团队的完整成员名单,包括成员姓名和管理员标记(admin flags)。
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 | 0 ~ 2.6.0 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-91972 | 7.5 HIGH | Vikunja before 2.6.0 Authentication Bypass via Unthrottled API |
| CVE-2026-91985 | 7.5 HIGH | Vikunja before 2.6.0 Privilege Escalation via Link Share Hash |
| CVE-2026-91973 | 7.5 HIGH | Vikunja before 2.6.0 Authentication Bypass via CalDAV BasicAuth |
| CVE-2026-91968 | 6.5 MEDIUM | vikunja before 2.6.0 Denial of Service via unbounded filter recursion |
| CVE-2026-91971 | 6.5 MEDIUM | Vikunja before 2.6.0 Denial of Service via Avatar Upload |
| CVE-2026-91979 | 6.5 MEDIUM | Vikunja before 2.6.0 Denial of Service via Decompression Bomb |
| CVE-2026-91970 | 6.5 MEDIUM | Vikunja before 2.6.0 Resource Exhaustion via Planka Migration |
| CVE-2026-91969 | 6.5 MEDIUM | vikunja before 2.6.0 Resource Exhaustion via CSV Migration |
| CVE-2026-91982 | 4.3 MEDIUM | Vikunja before 2.6.0 TOTP Secret Disclosure via API |
| CVE-2026-91981 | 4.3 MEDIUM | Vikunja before 2.6.0 User Enumeration via v2 API |
| CVE-2026-91983 | 4.3 MEDIUM | Vikunja before 2.6.0 API Token Scope Bypass via expand Parameter |
| CVE-2026-91984 | 4.3 MEDIUM | Vikunja before 2.6.0 Broken Object-Level Authorization via task-position |
No comments yet