在版本 2.7.0 之前的 Vikunja 0.22.0 中存在一个访问权限撤销不当的漏洞,该漏洞允许已被移除的协作者继续通过其创建的 Webhook 接收项目数据。即使访问权限已被撤销,前协作者仍可通过其 Webhook 接收任务标题和描述,包括在其权限被撤销后创建的内容。
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| go-vikunja | vikunja | 0.22.0< 2.7.0 |
affected |
2.7.0 |
unaffected |
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.22.0 ~ 2.7.0 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-111917 | 6.5 MEDIUM | Vikunja 2.3.0 before 2.7.0 WebSocket Authentication Ignores Session Revocation |
| CVE-2026-111922 | 6.3 MEDIUM | Vikunja 2.2.0 before 2.7.0 Permissive CORS Policy Trusting Localhost Origins |
| CVE-2026-111921 | 5.4 MEDIUM | Vikunja 0.13.0 before 2.7.0 Incorrect Authorization in Link Share Deletion |
| CVE-2026-111918 | 5.4 MEDIUM | Vikunja 1.0.0-rc0 before 2.7.0 Cross-Tenant Task Position Writes via Saved Filter Creation |
| CVE-2026-111920 | 4.3 MEDIUM | Vikunja 2.6.0 Broken Access Control via Inherited Project Permissions |
No comments yet