在 Vikunja 2.3.0 至 2.7.0(不含 2.7.0)版本中,存在一个会话验证不当的漏洞。由于 函数从未将 JWT 中的 (会话 ID)声明与会话表进行比对,攻击者即使在会话被撤销后,仍可持续保持 WebSocket 访问权限。持有被盗访问令牌的攻击者可在会话被删除或启用 TOTP(双因素认证)后,建立或维持对 端点的连接,并持续接收受害者的 推送消息,其中包含评论、任务和项目等敏感内容。
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| go-vikunja | vikunja | 2.3.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 | 2.3.0 ~ 2.7.0 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-111919 | 6.5 MEDIUM | Vikunja 0.22.0 before 2.7.0 Improper Access Revocation via Webhooks |
| 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