
I'm curious if Appwrite implements some kind of defense mehanism against Cross-Site Request Forgery attacks? This question is tied to the method or libraries Appwrite uses in client-side SDK-s to communicate with the Appwrite backend server. For Web SDK for instance, if the communication channel is implemented using the builtin fetch() coroutine, then CSRF protection must be configured manually. If a library like Axios is used, then CSRF protection is automatic, because Axios has it builtin. Therefore my question is, does Appwrite use the builtin fetch() coroutine and if it does, then has CSRF protection been implemented by the Appwrite team?

Appwrite shouldn't be susceptible to CSRF attacks because custom headers are required in the request. Feel free to create a POC if you find any security vulnerabilities and share them with security@appwrite.io

Oh we also validate the origin/referrer server-side to protect against CSRF
Recommended threads
- 1.7.x Style issue in the migration page
I am not able to select what to migrate because of the styling... the checkboxes are not showing on any of the appwrite versions 1.7.x. I tried other browsers, ...
- Website not responding on User session T...
The website is not responding after opening the user sessions tab. (The Chrome tab crashes and i need to open a new one )
- DigitalOcean Self-Hosted Restore Data & ...
I just went through this blog https://appwrite.io/blog/post/how-to-back-up-your-appwrite-data#copy-your-app-openssl-key-v1-environment-variable and created a ne...
