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-f27p-pw2p-9pr4 | Vikunja has a project duplication bypasses write-permission check on the target parent project |
Fri, 28 Aug 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Go-vikunja
Go-vikunja vikunja |
|
| Vendors & Products |
Go-vikunja
Go-vikunja vikunja |
Fri, 28 Aug 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Vikunja is an open-source self-hosted task management platform. From 0.21.0 until 2.4.0, the project duplication operation in pkg/models/project_duplicate.go allows an authenticated user who can read a source project to place its duplicate beneath an arbitrary target parent project. ProjectDuplicate.CanCreate calls parent.CanCreate on an unhydrated Project containing only the body supplied parent_project_id instead of calling parent.CanWrite, so the target parent write-permission check is skipped. The ordinary project creation path enforces that permission, but PUT /api/v1/projects/{project}/duplicate does not, allowing attacker-owned content to be injected into another user or team project hierarchy. This issue is fixed in version 2.4.0. | |
| Title | Vikunja: Project duplication bypasses write-permission check on the target parent project | |
| Weaknesses | CWE-285 CWE-863 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-08-28T19:59:25.820Z
Reserved: 2026-06-15T23:23:57.713Z
Link: CVE-2026-54766
No data.
Status : Received
Published: 2026-08-28T20:18:17.803
Modified: 2026-08-28T20:18:17.803
Link: CVE-2026-54766
No data.
OpenCVE Enrichment
Updated: 2026-08-28T21:00:04Z
Github GHSA