The API /api/v1/notes/{note_id} endpoint lacks proper authorization checks, allowing authenticated users to retrieve notes belonging to other users by guessing or enumerating UUIDs. This results in unauthorized disclosure of potentially sensitive or private user data.
Step 1: Log in to the application as a valid user (User A).
Step 2: Intercept or inspect the response from the endpoint GET /api/config.
Step 3: Observe the field "enable_notes": false in the JSON response.
Step 4: Manually change "enable_notes" to true using browser DevTools or by intercepting and modifying the response via a proxy like Burp Suite. (Please note, the occurrence of this API comes twice, hence modification needs to be made twice as well.)
Step 5: Observe the loaded frontend application; the previously hidden notes form will now be visible.
Fixed in commit de3317e26, first released in v0.8.11 (Mar 2026). All per-id note endpoints (GET /api/v1/notes/{id}, POST /api/v1/notes/{id}/update, POST /api/v1/notes/{id}/access/update, deletion) now enforce ownership: the handler fetches the note, then requires the caller to be admin, the note owner, or have an AccessGrants grant for the appropriate permission (read for retrieval, write for mutation). A non-owner with no grant receives 403.
Users on >= 0.8.11 are not affected.
{
"github_reviewed": true,
"severity": "MODERATE",
"nvd_published_at": "2026-05-15T22:16:56Z",
"github_reviewed_at": "2026-05-14T20:27:56Z",
"cwe_ids": [
"CWE-639"
]
}