Antiforgery tokens are reusable : <p>We use ASP.NET MVC's default Antiforgery technique.
Recently a security company did a scan of a form and made note that they could use the same <code>_RequestVerificationToken</code> combination (cookie + hidden field) multiple times.
Or how they put it: <em>"The CSRF token in the body is validated on server side but is not revoked after use even though the server
generates a new CSRF token."</em></p>

<p>After reading the documentation and multiple articles on the implementation of Antiforgery, it is my understanding that this is indeed possible as long as the session user matches the user in the tokens.</p>

<p>Part of their recommendation: <em>"Such tokens should, at
a minimum, be unique per user session"</em>
In my understanding this is already the case, except for anonymous users, correct?</p>

<p>My questions: Is this a security issue? How much of a risk is it? Is there a library that makes sure tokens are not reusable/invalidated.</p>

<p>If not, including an extra random token in session that will be reset on every request sounds like it would solve the issue.</p>
