Netsparker identified a possible Cross-Site Request Forgery.

CSRF is a very common vulnerability. It's an attack which forces a user to execute unwanted actions on a web application in which the user is currently authenticated.

Depending on the application, an attacker can mount any of the actions that can be done by the user such as adding a user, modifying content, deleting data. All the functionality that’s available to the victim can be used by the attacker. Only exception to this rule is a page that requires extra information that only the legitimate user can know (such as user’s password).
  • Send additional information in each HTTP request that can be used to determine whether the request came from an authorized source. This "validation token" should be hard to guess for attacker who does not already have access to the user's account. If a request is missing a validation token or the token does not match the expected value, the server should reject the request.

  • If you are posting form in ajax request, custom HTTP headers can be used to prevent CSRF because the browser prevents sites from sending custom HTTP headers to another site but allows sites to send custom HTTP headers to themselves using XMLHttpRequest.

    • For native XMLHttpRequest (XHR) object in JavaScript;
      xhr = new XMLHttpRequest();
      xhr.setRequestHeader('custom-header', 'value');
      For JQuery, if you want to add a custom header (or set of headers) to

      a. individual request

          url: 'foo/bar',
          headers: { 'x-my-custom-header': 'some value' }

      b. every request

          headers: { 'x-my-custom-header': 'some value' }
          beforeSend: function(xhr) {
              xhr.setRequestHeader('x-my-custom-header', 'some value');
PCI v3.1-6.5.9, PCI v3.2-6.5.9, CAPEC-62, WASC-9, OWASP 2013-A8
Vulnerability Inde
					<div class=

Vulnerability Index

You can search and find all vulnerabilities

Search Category


Search Vulnerability