CSRF Token Missing

The application is generally vulnerable to CSRF, meaning a malicious user can trick users to upload files, change password, mess records etc. The most robust way to defend against CSRF attacks is to include a CSRF token within relevant requests. The token must meet the following criteria: •Unpredictable with high entropy, as for session tokens in general. •Tied to the user's session. •Strictly validated in every case before the relevant action is executed. References: https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html https://portswigger.net/web-security/csrf/preventing