Vikunja 2.6.0 Broken Access Control via Inherited Project Permissions
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| go-vikunja | vikunja | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Go-vikunja | Vikunja |
|
||||||||
| Vikunja | Vikunja |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.191% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Go-vikunja
Go-vikunja vikunja |
|
| Vendors & Products |
Go-vikunja
Go-vikunja vikunja |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Vikunja 2.6.0 contains a broken access control flaw in getProjectAccessForUser (pkg/models/project_access.go), which resolves a user's effective project permission as the maximum over the project tree, silently overriding explicit lower-permission shares on sub-projects. A collaborator with write access on a parent project but read-only access to a child project can modify the child project's tasks and content. | |
| Title | Vikunja 2.6.0 Broken Access Control via Inherited Project Permissions | |
| First Time appeared |
Vikunja
Vikunja vikunja |
|
| Weaknesses | CWE-269 | |
| CPEs | cpe:2.3:a:vikunja:vikunja:2.6.0:*:*:*:*:*:*:* | |
| Vendors & Products |
Vikunja
Vikunja vikunja |
|
| References |
| |
| Metrics |
cvssV3_1
|