security: add Origin header validation for CSRF protection #413
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Security Issue Addressed
No CSRF Protection on POST (Low) - Previously relied only on CORS headers for protection. This PR adds explicit Origin header validation on state-changing requests.
Changes
backend/controllers/app_handlers.go:isOriginAllowed()function to validate request originsEnableCORS()to reject POST/PUT/DELETE requests from disallowed originsCSRF Protection Layers
With this PR, the application now has multiple layers of CSRF protection:
Test plan
🤖 Generated with Claude Code