Cross-project link-share deletion via unscoped lookup
Published Mar 24, 2026 · Updated Mar 24, 2026
Authorization bypass in Vikunja before 2.2.1 allows remote authenticated users to delete link shares from unrelated projects. The Delete method in pkg/models/link_sharing.go filters only on the attacker-supplied share ID and omits the project ID from its database predicate. Admin access to any project satisfies the permission check, enabling deletion of another project's share links and interruption of shared access.
Summary
What happened
Authorization bypass in Vikunja before 2.2.1 allows remote authenticated users to delete link shares from unrelated projects. The Delete method in pkg/models/link_sharing.go filters only on the attacker-supplied share ID and omits the project ID from its database predicate. Admin access to any project satisfies the permission check, enabling deletion of another project's share links and interruption of shared access.
The record
- CVE
- CVE-2026-33700
- Published
- Mar 24, 2026
- Updated
- Mar 24, 2026
- Vendor
- Vikunja
- Product
- Vikunja
- Classifications
- CWE-639, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 24, 2026CVE publishedPublication date reported by the CVE source.
- Mar 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vikunja advisory reproduction procedureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo