CSRF Tokens in Form Submissions
What you'll learn: How to embed CSRF tokens as hidden fields in HTML forms and handle token refresh when validation fails.
The Core Idea
When a user submits a form that changes server state (like updating a profile or transferring money), your backend needs proof the request came from your legitimate site, not a malicious one. You've already learned to read CSRF tokens from meta tags—now you'll embed them directly into forms as hidden fields so they're automatically sent with every submission.
Adding Hidden CSRF Token Fields
Include a hidden input field in every state-changing form:
<form method="POST" action="/update-profile">
<input type="hidden" name="csrf_token" id="csrf_token" value="">
<label>Email: <input type="email" name="email"></label>
<button type="submit">Update</button>
</form>
Populate the token value from your meta tag (as you learned previously):
const csrfToken = document.querySelector('meta[name="csrf-token"]').getAttribute('content');
document.getElementById('csrf_token').value = csrfToken;
Handling Token Refresh on Validation Errors
When the server rejects a form submission due to an invalid or expired CSRF token, it typically returns a new token. Your frontend must:
- Detect the error (check response status or error message)
- Extract the new token from the response or a refreshed meta tag
- Update the hidden field before allowing resubmission
form.addEventListener('submit', async (e) => {
e.preventDefault();
const response = await fetch('/update-profile', {
method: 'POST',
body: new FormData(form)
});
if (response.status === 403) {
// Token expired—refresh it
const newToken = response.headers.get('X-CSRF-Token');
document.getElementById('csrf_token').value = newToken;
// Optionally retry or alert user
}
});
Key Takeaway: Embed CSRF tokens as hidden form fields and always refresh them when validation fails to maintain uninterrupted, secure form submissions.