Click here to Skip to main content
15,120,883 members
Articles / Web Development / ASP.NET
Posted 15 Sep 2014

Tagged as


15 bookmarked

Prevent MVC Application from Cross Site Request Forgery Attacks

Rate me:
Please Sign up or sign in to vote.
4.70/5 (19 votes)
15 Sep 2014CPOL2 min read
First step towards securing MVC applications


All web application platforms are potentially vulnerable to CSRF (Cross-Site Request Forgery) attacks. The best way to prevent this attack in MVC application is to use Anti-Forgery token.

Consider a banking website "" contains an action method DeleteUser in User Controller. When a web request comes from a client, the controller fetches the user id from session and deletes the user from database. Consider one hacker created a site "" and it contain one button 'Latest songs'. The button click event calls the "". A user is logged in "" and he is visiting "" using the same browser with another tab. When he clicking the 'Latest songs' button, his account will delete from the bank database. To avoid these type of unwanted requests from other sites, MVC application developers use Anti-Forgery Token.

Anti-Forgery Token is mainly used in form POST actions to verify the source of the POST data. In this method, for each page request, the web server sends a cookie to the client browser. While posting the data or next request time, the web server uses this cookie for client authentication. If the request is coming from an unauthorized site, the cookie will be null or invalid. By adding [ValidateAntiForgeryToken] above the controller and @Html.AntiForgeryToken() in the view page, we can prevent cross site requests forgery.

Using the Code

The below code illustrates how Anti-Forgery Token Cross Site Request Forgery:

Without Anti-Forgery Token

1. Controller (Controller for deleting the user account)

public class UserController : Controller
       public ActionResult DeleteUser()
           var userId = (int)Session["userId"];
           DeleteUserFromDb(userId);  //Function for deleting the user from Database
          return View();

2. View (Button for deleting the user account in Bank page)

@using (Html.BeginForm("DeleteUser", "User"))
    <input type="submit" value="Delete My Account" />

With Anti-Forgery Token

1. Controller

public class UserController : Controller
        public ActionResult DeleteUser()
            var userId = (int)Session["userId"];            
            DeleteUserFromDb(userId);//Function for deleting the user from Database
            return View();

2. View

@using (Html.BeginForm("DeleteUser", "User"))
    <input type="submit" value="Delete My Account" />

Cross Site Request Error

Server Error in '/' Application.

The required anti-forgery cookie "__RequestVerificationToken" is not present.

Description: An unhandled exception occurred during the execution of the current web request. 
Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.Web.Mvc.HttpAntiForgeryException: 
The required anti-forgery cookie "__RequestVerificationToken" is not present.

Points of Interest

You would be wondering that I have mentioned the error and have not mentioned how to resolve that. This is a simple error that arises if you are not using the Antiforgery token attributes at appropriate places. As in, if we specify the [ValidateAntiForgeryToken] in the controller and miss out specifying in the View page posting the form, this gives rise to this exception and also prevents posting the data to the server.


I came through this exception after using this valuable asset that MVC provides us with. This is a real handy attribute that is the first stage of security which an MVC developer should have in mind.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Shemeemsha (ഷെമീംഷ)
Software Developer (Junior)
India India
"MVC 70-486" and "OCJP" certified.
Email :-

Comments and Discussions

Questionmultiple post Pin
trickster_ahmet8-Nov-17 21:36
Membertrickster_ahmet8-Nov-17 21:36 
QuestionVery nice Pin
19sanjeev9-Oct-14 19:36
professional19sanjeev9-Oct-14 19:36 
Suggestionsuggestion Pin
paulkth17-Sep-14 10:27
Memberpaulkth17-Sep-14 10:27 
GeneralRe: suggestion Pin
Shemeemsha (ഷെമീംഷ)17-Sep-14 20:37
MemberShemeemsha (ഷെമീംഷ)17-Sep-14 20:37 
QuestionVery Nice Pin
Suraj Sahoo | Coding Passion17-Sep-14 9:59
professionalSuraj Sahoo | Coding Passion17-Sep-14 9:59 
AnswerRe: Very Nice Pin
Shemeemsha (ഷെമീംഷ)17-Sep-14 20:31
MemberShemeemsha (ഷെമീംഷ)17-Sep-14 20:31 
GeneralGood article Pin
Amit Pandey 216-Sep-14 22:20
professionalAmit Pandey 216-Sep-14 22:20 
GeneralRe: Good article Pin
Shemeemsha (ഷെമീംഷ)16-Sep-14 22:40
MemberShemeemsha (ഷെമീംഷ)16-Sep-14 22:40 
GeneralMy vote of 5 Pin
Humayun Kabir Mamun16-Sep-14 1:26
MemberHumayun Kabir Mamun16-Sep-14 1:26 
GeneralRe: My vote of 5 Pin
Shemeemsha (ഷെമീംഷ)16-Sep-14 5:33
MemberShemeemsha (ഷെമീംഷ)16-Sep-14 5:33 
GeneralNice article Pin
suhel_khan16-Sep-14 1:19
professionalsuhel_khan16-Sep-14 1:19 
GeneralRe: Nice article Pin
Shemeemsha (ഷെമീംഷ)16-Sep-14 5:33
MemberShemeemsha (ഷെമീംഷ)16-Sep-14 5:33 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.