CVE Vulnerabilities

CVE-2011-4947

Cross-Site Request Forgery (CSRF)

Published: Aug 31, 2012 | Modified: Apr 11, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu
root.io logo minimus.io logo echo.ai logo

Cross-site request forgery (CSRF) vulnerability in e107_admin/users_extended.php in e107 before 0.7.26 allows remote attackers to hijack the authentication of administrators for requests that insert cross-site scripting (XSS) sequences via the user_include parameter.

Weakness

The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Affected Software

NameVendorStart VersionEnd Version
E107E107*0.7.24 (including)
E107E1070.7 (including)0.7 (including)
E107E1070.7.0 (including)0.7.0 (including)
E107E1070.7.1 (including)0.7.1 (including)
E107E1070.7.2 (including)0.7.2 (including)
E107E1070.7.3 (including)0.7.3 (including)
E107E1070.7.4 (including)0.7.4 (including)
E107E1070.7.5 (including)0.7.5 (including)
E107E1070.7.6 (including)0.7.6 (including)
E107E1070.7.7 (including)0.7.7 (including)
E107E1070.7.8 (including)0.7.8 (including)
E107E1070.7.9 (including)0.7.9 (including)
E107E1070.7.10 (including)0.7.10 (including)
E107E1070.7.11 (including)0.7.11 (including)
E107E1070.7.12 (including)0.7.12 (including)
E107E1070.7.13 (including)0.7.13 (including)
E107E1070.7.14 (including)0.7.14 (including)
E107E1070.7.15 (including)0.7.15 (including)
E107E1070.7.16 (including)0.7.16 (including)
E107E1070.7.17 (including)0.7.17 (including)
E107E1070.7.18 (including)0.7.18 (including)
E107E1070.7.19 (including)0.7.19 (including)
E107E1070.7.20 (including)0.7.20 (including)
E107E1070.7.21 (including)0.7.21 (including)
E107E1070.7.22 (including)0.7.22 (including)

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 [REF-1482].
  • 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]

References