Description
Vikunja from 2.2.0 before 2.7.1 contains an authorization bypass vulnerability that allows holders of tokens scoped only to projects_webhooks to manage the owner's user-level webhooks by supplying user_id in request bodies. Attackers can register user webhooks to their own receiver to obtain reminders and task payloads from all owner projects, and read, change or delete existing user webhooks.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| go-vikunja | vikunja | 2.2.0 – < 2.7.1 | 2.7.1 |
References
- GitHub Security Advisory (GHSA-5f6v-j6xm-wwj9) vendor-advisory
- VulnCheck Advisory: Vikunja 2.2.0 before 2.7.1 Token Scope Bypass via Project Webhook Endpoints third-party-advisory