CVE Vulnerabilities


Cross-Site Request Forgery (CSRF)

Published: Nov 24, 2014 | Modified: Dec 01, 2020
CVSS 3.x
CVSS 2.x

Multiple cross-site request forgery (CSRF) vulnerabilities in the Forum module in Moodle through 2.4.11, 2.5.x before 2.5.9, 2.6.x before 2.6.6, and 2.7.x before 2.7.3 allow remote attackers to hijack the authentication of arbitrary users for requests that set a tracking preference within (1) mod/forum/deprecatedlib.php, (2) mod/forum/forum.js, (3) mod/forum/index.php, or (4) mod/forum/lib.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
Moodle Moodle * 2.4.11
Moodle Moodle 2.5.0 2.5.0
Moodle Moodle 2.5.1 2.5.1
Moodle Moodle 2.5.2 2.5.2
Moodle Moodle 2.5.3 2.5.3
Moodle Moodle 2.5.4 2.5.4
Moodle Moodle 2.5.5 2.5.5
Moodle Moodle 2.5.6 2.5.6
Moodle Moodle 2.5.7 2.5.7
Moodle Moodle 2.5.8 2.5.8
Moodle Moodle 2.6.0 2.6.0
Moodle Moodle 2.6.1 2.6.1
Moodle Moodle 2.6.2 2.6.2
Moodle Moodle 2.6.3 2.6.3
Moodle Moodle 2.6.4 2.6.4
Moodle Moodle 2.6.5 2.6.5
Moodle Moodle 2.7.0 2.7.0
Moodle Moodle 2.7.1 2.7.1
Moodle Moodle 2.7.2 2.7.2
Moodle Ubuntu artful *
Moodle Ubuntu lucid *
Moodle Ubuntu precise *
Moodle Ubuntu trusty *
Moodle Ubuntu upstream *
Moodle Ubuntu utopic *
Moodle Ubuntu vivid *
Moodle Ubuntu wily *
Moodle Ubuntu yakkety *
Moodle Ubuntu zesty *

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]