go-vikunja up to 2.2.0 /api/v1/projects/ authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 1.12 |
Summary
A vulnerability described as problematic has been identified in go-vikunja vikunja up to 2.2.0. This impacts an unknown function of the file /api/v1/projects/. The manipulation results in authorization. This vulnerability is reported as CVE-2026-33700. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, was found in go-vikunja vikunja up to 2.2.0. Affected is an unknown code block of the file /api/v1/projects/. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on integrity, and availability. CVE summarizes:
Vikunja is an open-source self-hosted task management platform. Prior to version 2.2.1, the `DELETE /api/v1/projects/:project/shares/:share` endpoint does not verify that the link share belongs to the project specified in the URL. An attacker with admin access to any project can delete link shares from other projects by providing their own project ID combined with the target share ID. Version 2.2.1 patches the issue.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-33700 since 03/23/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. Additional levels of successful authentication are required for exploitation. There are known technical details, but no exploit is available.
Upgrading to version 2.2.1 eliminates this vulnerability. The upgrade is hosted for download at vikunja.io.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.8VulDB Meta Temp Score: 3.7
VulDB Base Score: 3.8
VulDB Temp Score: 3.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: vikunja 2.2.1
Timeline
03/23/2026 CVE reserved03/24/2026 Advisory disclosed
03/24/2026 VulDB entry created
03/29/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-f95f-77jx-fcjc
Status: Confirmed
CVE: CVE-2026-33700 (🔒)
GCVE (CVE): GCVE-0-2026-33700
GCVE (VulDB): GCVE-100-352812
Entry
Created: 03/24/2026 17:33Updated: 03/29/2026 03:20
Changes: 03/24/2026 17:33 (68), 03/29/2026 03:20 (1)
Complete: 🔍
Cache ID: 216:904:103
No comments yet. Languages: en.
Please log in to comment.