| Title | Archivy Project Archivy 1.7.7 Cross-Site Request Forgery |
|---|
| Description | Flask-WTF CSRF protection is explicitly exempted for the entire API blueprint (csrf.exempt(api_bp)) and the bookmark-saving endpoint (@csrf.exempt on /save_from_bookmarklet). Since the application does not configure SESSION_COOKIE_SAMESITE, session cookies carry no SameSite attribute. In same-site deployment scenarios (same host different port, same LAN — the typical model for self-hosted tools), an attacker-controlled page can auto-submit forms to create arbitrary bookmarks with attacker-controlled HTML content under the authenticated user's identity, without any CSRF token. All API write endpoints (create/update/delete bookmarks, notes, folders) are equally unprotected. Verified on a live instance: POST without CSRF token successfully created a bookmark (302 → /dataobj/1) and a note via API (200, note_id=2). |
|---|
| Source | ⚠️ https://github.com/BlkSword/POC/blob/main/archivy-csrf-vulnerability-report.md |
|---|
| User | XiaoHei (UID 92738) |
|---|
| Submission | 07/23/2026 14:34 (2 months ago) |
|---|
| Moderation | 09/23/2026 17:23 (2 months later) |
|---|
| Status | Duplicate |
|---|
| VulDB entry | 189080 [archivy cross-site request forgery] |
|---|
| Points | 0 |
|---|