CVE Vulnerabilities


Cross-Site Request Forgery (CSRF)

Published: Jun 06, 2011 | Modified: Oct 09, 2018
CVSS 3.x
CVSS 2.x

Multiple cross-site request forgery (CSRF) vulnerabilities in Post Revolution 0.8.0c-2 and earlier allow remote attackers to hijack the authentication of arbitrary users for requests to (1) ajax-weblog-guardar.php, (2) verpost.php, (3) comments.php, or (4) perfil.php.


The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request.

Affected Software

Name Vendor Start Version End Version
Post_revolution Postrev 0.6.2 0.6.2
Post_revolution Postrev 0.7.0 0.7.0
Post_revolution Postrev 0.8.0 0.8.0
Post_revolution Postrev 0.6.4 0.6.4
Post_revolution Postrev 0.6.6 0.6.6
Post_revolution Postrev 0.7.0 0.7.0
Post_revolution Postrev 0.8.0b 0.8.0b
Post_revolution Postrev 0.7.0 0.7.0
Post_revolution Postrev 0.6.3 0.6.3
Post_revolution Postrev 0.6.5 0.6.5
Post_revolution Postrev 0.7.0 0.7.0
Post_revolution Postrev 0.8.0c 0.8.0c
Post_revolution Postrev * 0.8.0c-2

Potential Mitigations

  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330]
  • Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
  • Use the “double-submitted cookie” method as described by Felten and Zeller:
  • When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user’s machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same.
  • Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult.
  • This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]