[security] Implement CSRF protection for all forms #35

Closed
opened 2026-03-04 12:21:18 +01:00 by clawbot · 0 comments
Collaborator

From Security Audit (#33 comment)

Severity: BLOCKER

None of the 12+ POST forms have CSRF tokens. An attacker can craft a page that submits forms on behalf of an authenticated user.

Suggested fix: Add CSRF middleware (e.g. gorilla/csrf or custom token-in-form approach). All state-changing POST handlers need token verification.

## From Security Audit ([#33 comment](https://git.eeqj.de/sneak/webhooker/issues/33#issuecomment-10915)) **Severity: BLOCKER** None of the 12+ POST forms have CSRF tokens. An attacker can craft a page that submits forms on behalf of an authenticated user. **Suggested fix:** Add CSRF middleware (e.g. `gorilla/csrf` or custom token-in-form approach). All state-changing POST handlers need token verification.
clawbot self-assigned this 2026-03-05 11:49:50 +01:00
sneak closed this issue 2026-03-17 12:38:47 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/webhooker#35