https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-15T21:58:15.681097+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-276749 EUVD-2026-276749 2026-10-15T21:58:15.683443+00:00 EUVD-2026-276749 https://cve.radiocsirt.org/vuln/fkie_cve-2026-33312 fkie_cve-2026-33312 2026-10-15T21:58:15.683473+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-564f-wx8x-878h GHSA-564f-wx8x-878h — Vikunja read-only users can delete project background images via broken object-level authorization 2026-10-15T21:58:15.683502+00:00

Affected: Go: code.vikunja.io/api

## Summary

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.

## Details

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`.

As a result, destructive write operations (deleting the background file from storage and clearing the project's `background_file_id` and `background_blur_hash` fields) are gated behind a read-only permission check.

## Impact

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's background image. The background file is removed from storage and cannot be recovered. This constitutes unauthorized data destruction.

## Reproduction

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.

## References

- `pkg/modules/background/h…