Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-v479-vf79-mg83 | Vikunja: Scoped API tokens with projects.background permission can delete project backgrounds |
Fri, 17 Apr 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Vikunja
Vikunja vikunja |
|
| CPEs | cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Vikunja
Vikunja vikunja |
Wed, 15 Apr 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 13 Apr 2026 13:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Go-vikunja
Go-vikunja vikunja |
|
| Vendors & Products |
Go-vikunja
Go-vikunja vikunja |
Fri, 10 Apr 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, Vikunja's scoped API token enforcement for custom project background routes is method-confused. A token with only projects.background can successfully delete a project background, while a token with only projects.background_delete is rejected. This is a scoped-token authorization bypass. This vulnerability is fixed in 2.3.0. | |
| Title | Vikunja's Scoped API tokens with projects.background permission can delete project backgrounds | |
| Weaknesses | CWE-836 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-15T14:45:18.303Z
Reserved: 2026-04-09T01:41:38.536Z
Link: CVE-2026-40103
Updated: 2026-04-15T14:45:14.173Z
Status : Analyzed
Published: 2026-04-10T17:17:13.143
Modified: 2026-04-17T22:03:51.840
Link: CVE-2026-40103
No data.
OpenCVE Enrichment
Updated: 2026-04-13T13:00:25Z
Github GHSA