medium5.3
CVE-2026-123506
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 own…
Impact
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.
An attacker can exploit this over the network, with a regular user account, without any action by a user. If it succeeds: low risk of data being read, low risk of data or systems being changed.
Affected products · Go-vikunja
| Product | Affected versions |
|---|---|
| Vikunja | from 2.2.0 before 2.7.1 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-5f6v-j6xm-wwj9
- https://www.vulncheck.com/advisories/vikunja-2.2.0-before-2.7.1-token-scope-bypass-via-project-webhook-endpoints
- https://github.com/advisories/GHSA-2fc5-hwxx-39f7
- https://nvd.nist.gov/vuln/detail/CVE-2026-123506