by aramrami

OWASP CSRFGuard 3.1.0

144 Stars 118 Forks Last release: almost 6 years ago (3.1.0) 168 Commits 1 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:


We are working on new version of CSRFGuard including a lot of merge request with goood proposals and also a new code to fix known issues on XSS attacks that bypass CSRFGuard.

Target date for the new relase 4.0 : end of Q2 2020

We need your help. If you want to give few hours of your time to help us please contact me.

OWASP CSRFGuard 3.1.0


BSD License, All rights reserved.


Welcome to the home of the OWASP CSRFGuard Project! OWASP CSRFGuard is a library that implements a variant of the synchronizer token pattern to mitigate the risk of Cross-Site Request Forgery (CSRF) attacks. The OWASP CSRFGuard library is integrated through the use of a JavaEE Filter and exposes various automated and manual ways to integrate per-session or pseudo-per-request tokens into HTML. When a user interacts with this HTML, CSRF prevention tokens (i.e. cryptographically random synchronizer tokens) are submitted with the corresponding HTTP request. It is the responsibility of OWASP CSRFGuard to ensure the token is present and is valid for the current HTTP request. Any attempt to submit a request to a protected resource without the correct corresponding token is viewed as a CSRF attack in progress and is discarded. Prior to discarding the request, CSRFGuard can be configured to take one or more actions such as logging aspects of the request and redirecting the user to a landing page. The latest release enhances this strategy to support the optional verification of HTTP requests submitted using Ajax as well as the optional verification of referrer headers.

Project Lead

The CSRFGuard project is run by Azzeddine RAMRAMI. He can be contacted at azzeddine.ramrami AT owasp.org.


OWASP CSRFGuard 3.1.0 is offered under the BSD license

Using with Maven

OWASP CSRFGuard 3.1.0 will be available on Maven Central. Add the following dependency to your Maven POM file to use the library:


Building the code

  1. Make sure that you have Apache Maven 3.0.4 or higher installed;
  2. Make sure that you have GPG installed and a secret key generated with it;
  3. Clone this repository locally;
  4. Build the
    project first as
    cd csrfguard
    followed by
    mvn clean install
  5. Build and run the
    project as
    cd ../csrfguard-test
    followed by
    mvn clean package tomcat7:run
  6. Use a web browser to access
    to open the home page of the test project.

Uploading to the Maven Central repository

  1. Follow the Sonatype Open-Source Project Maven Repository Usage Guide to create a Sonatype user account;
  2. Next, open a support request to get your newly created username added to the Maven groupId
  3. Once the support request has been completed, follow the instructions in the Sonatype Maven repository usage guide mentioned above to upload new versions to the Maven Central repository.

Email List

You can sign up for the OWASP CSRFGuard email list here.

Last News

An important security fix has been applied to the CSRFGuard version 3.0.

Do a token pre-fetch on every page.

Instead of hard coding the CSRF token, we send a POST request to fetch the token and populate the JS variable.

Thanks to Ahamed Nafeez [email protected] for this fix.

CSRFGuard in Maven Central

You can download a binary version from Maven Central here:


Thanks to Trent Schmidt and Joel Orlina (JIRA) for there help.

CSRFGuard integration with a JSF application

Yi SONG create for CSRFGuard project a simple example to demostrate the CSRFGuard integration with a JSF application.

The original JSF project is taken from https://mkyong.com/jsf2/jsf-2-0-hello-world-example/

After integrating with csrfguard, the project has been tested on netbean 8.2 with glassfish 4.1.1

Yi SONG Bio:

Yi SONG received my master of engineering in China in 2006. Then I start work for Axalto, then Gemalto and then Thales till now. He has 3 years experience on smartcard development, 10 years experience on cryptography and hardware security module. Since end of 2018, his work is focusing on web application and cloud.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.