donetick up to 0.1.82 History Deletion model.go CanDeleteHistory AssignedTo improper authorization

Summaryinfo

A vulnerability classified as problematic has been found in donetick up to 0.1.82. This affects the function CanDeleteHistory of the file internal/chore/model/model.go of the component History Deletion Handler. This manipulation of the argument AssignedTo causes improper authorization. This vulnerability appears as CVE-2026-112045. The attack may be initiated remotely. In addition, an exploit is available. The project maintainer explains: "The concerns about "IDOR" framing seem to be overstated in my opinion (...), as Circle members are already trusted collaborators. We will address this issue. However, since the impact is limited to trusted members within the same circle, I would classify this as a bug rather than a security vulnerability."

Detailsinfo

A vulnerability was found in donetick up to 0.1.82. It has been declared as problematic. Affected by this vulnerability is the function CanDeleteHistory of the file internal/chore/model/model.go of the component History Deletion Handler. The manipulation of the argument AssignedTo with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect integrity, and availability.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-112045. The exploitation appears to be easy. The attack can be launched remotely. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.

It is possible to download the exploit at github.com. It is declared as proof-of-concept. The project maintainer explains: "The concerns about "IDOR" framing seem to be overstated in my opinion (...), as Circle members are already trusted collaborators. We will address this issue. However, since the impact is limited to trusted members within the same circle, I would classify this as a bug rather than a security vulnerability."

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• donetick

Version

• 0.1.0
• 0.1.1
• 0.1.2
• 0.1.3
• 0.1.4
• 0.1.5
• 0.1.6
• 0.1.7
• 0.1.8
• 0.1.9
• 0.1.10
• 0.1.11
• 0.1.12
• 0.1.13
• 0.1.14
• 0.1.15
• 0.1.16
• 0.1.17
• 0.1.18
• 0.1.19
• 0.1.20
• 0.1.21
• 0.1.22
• 0.1.23
• 0.1.24
• 0.1.25
• 0.1.26
• 0.1.27
• 0.1.28
• 0.1.29
• 0.1.30
• 0.1.31
• 0.1.32
• 0.1.33
• 0.1.34
• 0.1.35
• 0.1.36
• 0.1.37
• 0.1.38
• 0.1.39
• 0.1.40
• 0.1.41
• 0.1.42
• 0.1.43
• 0.1.44
• 0.1.45
• 0.1.46
• 0.1.47
• 0.1.48
• 0.1.49
• 0.1.50
• 0.1.51
• 0.1.52
• 0.1.53
• 0.1.54
• 0.1.55
• 0.1.56
• 0.1.57
• 0.1.58
• 0.1.59
• 0.1.60
• 0.1.61
• 0.1.62
• 0.1.63
• 0.1.64
• 0.1.65
• 0.1.66
• 0.1.67
• 0.1.68
• 0.1.69
• 0.1.70
• 0.1.71
• 0.1.72
• 0.1.73
• 0.1.74
• 0.1.75
• 0.1.76
• 0.1.77
• 0.1.78
• 0.1.79
• 0.1.80
• 0.1.81
• 0.1.82

Website

• Product: https://github.com/donetick/donetick/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #1009027: https://github.com/donetick/ donetick commit 0ca432c1f7731ef9c4c2f00aad7f2f845ef9c2b3 Improper Authorization (by geochen)

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion