https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 15 Oct 2026 21:57:47 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-276749 EUVD-2026-276749 https://cve.radiocsirt.org/vuln/euvd-2026-276749 https://cve.radiocsirt.org/vuln/fkie_cve-2026-33312 <p>Vikunja is an open-source self-hosted task management platform. Starting in version 0.20.2 and prior to version 2.2.0, the `DELETE /api/v1/projects/:project/background` endpoint checks `CanRead` permission instead of `CanUpdate`, allowing any user with read-only access to a project to permanently delete its background image. Version 2.2.0 fixes the issue.</p> <p>Vikunja is an open-source self-hosted task management platform. Starting in version 0.20.2 and prior to version 2.2.0, the `DELETE /api/v1/projects/:project/background` endpoint checks `CanRead` permission instead of `CanUpdate`, allowing any user with read-only access to a project to permanently delete its background image. Version 2.2.0 fixes the issue.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-33312 https://cve.radiocsirt.org/vuln/ghsa-564f-wx8x-878h <p><strong>Affected:</strong> Go: code.vikunja.io/api</p> <p>## Summary</p> <p>The `DELETE /api/v1/projects/:project/background` endpoint checks `CanRead` permission instead of `CanUpdate`, allowing any user with read-only access to a project to permanently delete its background image.</p> <p>## Details</p> <p>The `RemoveProjectBackground` handler (`pkg/modules/background/handler/background.go`) reuses `checkProjectBackgroundRights`, a helper originally written for the read-only `GetProjectBackground` endpoint. This helper only verifies `CanRead` permission. In contrast, the handler for *setting* a background (`setBackgroundPreparations`) correctly checks `CanUpdate`.</p> <p>As a result, destructive write operations (deleting the background file from storage and clearing the project&#39;s `background_file_id` and `background_blur_hash` fields) are gated behind a read-only permission check.</p> <p>## Impact</p> <p>A user with read-only access to a project — via direct sharing, team membership, link share tokens with read permission, or read-scoped API tokens — can permanently delete the project&#39;s background image. The background file is removed from storage and cannot be recovered. This constitutes unauthorized data destruction.</p> <p>## Reproduction</p> <p>1. User A creates a project and sets a background image. 2. User A shares the project with User B with **read-only** permission. 3. User B sends: `DELETE /api/v1/projects/{project_id}/background` with a valid auth token. 4. The request succeeds. The background image is permanently deleted.</p> <p>## References</p> <p>- `pkg/modules/background/h…</p> <p><strong>Affected:</strong> Go: code.vikunja.io/api</p> <p>## Summary</p> <p>The `DELETE /api/v1/projects/:project/background` endpoint checks `CanRead` permission instead of `CanUpdate`, allowing any user with read-only access to a project to permanently delete its background image.</p> <p>## Details</p> <p>The `RemoveProjectBackground` handler (`pkg/modules/background/handler/background.go`) reuses `checkProjectBackgroundRights`, a helper originally written for the read-only `GetProjectBackground` endpoint. This helper only verifies `CanRead` permission. In contrast, the handler for *setting* a background (`setBackgroundPreparations`) correctly checks `CanUpdate`.</p> <p>As a result, destructive write operations (deleting the background file from storage and clearing the project&#39;s `background_file_id` and `background_blur_hash` fields) are gated behind a read-only permission check.</p> <p>## Impact</p> <p>A user with read-only access to a project — via direct sharing, team membership, link share tokens with read permission, or read-scoped API tokens — can permanently delete the project&#39;s background image. The background file is removed from storage and cannot be recovered. This constitutes unauthorized data destruction.</p> <p>## Reproduction</p> <p>1. User A creates a project and sets a background image. 2. User A shares the project with User B with **read-only** permission. 3. User B sends: `DELETE /api/v1/projects/{project_id}/background` with a valid auth token. 4. The request succeeds. The background image is permanently deleted.</p> <p>## References</p> <p>- `pkg/modules/background/h…</p> https://cve.radiocsirt.org/vuln/ghsa-564f-wx8x-878h