go-vikunja up to 2.2.x projects.background_delete password hash instead of password for authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in go-vikunja vikunja up to 2.2.x. Affected is the function projects.background_delete. Performing a manipulation results in use of password hash instead of password for authentication.
This vulnerability was named CVE-2026-40103. The attack may be initiated remotely. There is no available exploit.
You should upgrade the affected component.
Details
A vulnerability was found in go-vikunja vikunja up to 2.2.x. It has been classified as problematic. This affects the function projects.background_delete. The manipulation with an unknown input leads to a use of password hash instead of password for authentication vulnerability. CWE is classifying the issue as CWE-836. The product records password hashes in a data store, receives a hash of a password from a client, and compares the supplied hash to the hash obtained from the data store. This is going to have an impact on integrity. The summary by CVE is:
Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, Vikunja's scoped API token enforcement for custom project background routes is method-confused. A token with only projects.background can successfully delete a project background, while a token with only projects.background_delete is rejected. This is a scoped-token authorization bypass. This vulnerability is fixed in 2.3.0.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-40103 since 04/09/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1550.002 according to MITRE ATT&CK.
Upgrading to version 2.3.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 6a0f39b252a81fa4b19dc56dc889183acc9225ae is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.3
CNA Vector (GitHub_M): 🔒
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: Use of password hash instead of password for authenticationCWE: CWE-836
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.3.0
Patch: 6a0f39b252a81fa4b19dc56dc889183acc9225ae
Timeline
04/09/2026 CVE reserved04/10/2026 Advisory disclosed
04/10/2026 VulDB entry created
04/10/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-v479-vf79-mg83
Status: Confirmed
CVE: CVE-2026-40103 (🔒)
GCVE (CVE): GCVE-0-2026-40103
GCVE (VulDB): GCVE-100-356883
Entry
Created: 04/10/2026 20:23Changes: 04/10/2026 20:23 (67)
Complete: 🔍
Cache ID: 216:DE5:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.