/

CVE-2026-55065

Severity:

HIGH RISK

(8.1)

Broken Object Authorization (CWE-639) in Vikunja Views

CVE-2026-55065

Deferred

Vulnerability type

Category:

Broken Object-Level Authorization

CWE:

CWE-285, CWE-639

Impact:

Cross-tenant data destruction

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Vikunja contains a broken object-level authorization flaw in its project view deletion API. An authenticated user may reference a view belonging to another project and cause its Kanban assignments and ordering data to be deleted when the request uses an attacker-controlled project identifier.

Affected context

The issue occurs in Vikunja deployments using the affected project view deletion endpoint. It becomes risky when an authenticated user can submit a view identifier independently of the project identifier used for authorization, and the deletion workflow performs follow-up cleanup without confirming that the view belongs to the authorized project.

Exploit preconditions

  • Attack surface: Authenticated HTTP API for project view deletion
  • Required access: A valid Vikunja user account and permission to access a project
  • Trigger point: A request to delete a project view with mismatched project and view identifiers
  • Why exploitation is possible: Authorization checks the supplied project but do not establish ownership of the referenced view, while subsequent cleanup uses only the view identifier

Why this happens

The underlying bug is an object authorization mismatch. The application authorizes an attacker-controlled project identifier but fails to verify that the target view is associated with that project, which maps to CWE-639, Authorization Bypass Through User-Controlled Key. The deletion routine also continues after a scoped delete affects no rows and performs related cleanup using only the view identifier, allowing records from another project to be modified or removed.

Potential impact

  • An authenticated user could delete task bucket assignments belonging to another project
  • An attacker could disrupt Kanban ordering and board presentation
  • Cross-tenant integrity violations may occur while the victim view and tasks remain intact
  • Users and teams could experience operational disruption or loss of planning metadata

General mitigation guidance

Mitigation generally focuses on enforcing ownership and authorization at

every object boundary in the deletion workflow.

Common defensive patterns include:

  • Resolve the target view through the authorized project context rather than trusting independent identifiers
  • Verify object ownership before performing the primary deletion or any related cleanup
  • Use transactionally consistent, scoped deletes that include both project and view identity
  • Treat zero-row or ownership-mismatch results as authorization or not-found failures
  • Apply least-privilege database permissions and tenant-aware data access policies
  • Add regression tests for cross-project identifier substitution and partial-delete behavior

How teams detect issues like this

Organizations can look for this issue through:

  • Static analysis rules identifying delete operations that use user-controlled object identifiers without relationship checks
  • Code review signals where authorization uses one path parameter but database cleanup uses another identifier
  • Tests that combine valid project identifiers with views from unrelated projects
  • API policy checks requiring object ownership validation before destructive actions
  • Audit-log monitoring for unusual deletion attempts involving mismatched project and view references

Automated security review tools may help identify missing relationship predicates and authorization checks.

Sources

SourceLink
github.comgithub.com/go-vikunja/vikunja/commit/6895a7765ef1667be4b79df29549d33b9e1ca9ca
github.comgithub.com/go-vikunja/vikunja/pull/3239
github.comgithub.com/go-vikunja/vikunja/releases/tag/v2.4.0
github.comgithub.com/go-vikunja/vikunja/security/advisories/GHSA-gg93-x632-9ccv

Frequently asked

questions

An authenticated user is generally required. The account must be able to reach

the project view deletion API, but it may not need access to the victim's

project or view.

The issue affects deletion of project views and the subsequent cleanup of

task bucket and task position records associated with the referenced view.

Authorize the target view within the same project-scoped query used for the

request, then perform all related deletes using verified project and view

ownership constraints.

Use centralized object-level authorization, enforce tenant-aware database

predicates, reject mismatched identifiers, and test destructive endpoints with

cross-project object references.

Find out what's already
exploitable in your codebase.