CVE Vulnerabilities

CVE-2014-3907

Cross-Site Request Forgery (CSRF)

Published: Aug 26, 2014 | Modified: Aug 27, 2014
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

Cross-site request forgery (CSRF) vulnerability in the MailPoet Newsletters (wysija-newsletters) plugin before 2.6.11 for WordPress allows remote attackers to hijack the authentication of arbitrary users.

Weakness

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
Mailpoet_newsletters Mailpoet 2.1.1 2.1.1
Mailpoet_newsletters Mailpoet 2.0.6 2.0.6
Mailpoet_newsletters Mailpoet 1.1.5 1.1.5
Mailpoet_newsletters Mailpoet 2.0 2.0
Mailpoet_newsletters Mailpoet 2.6.6 2.6.6
Mailpoet_newsletters Mailpoet 2.1.2 2.1.2
Mailpoet_newsletters Mailpoet 2.6.3 2.6.3
Mailpoet_newsletters Mailpoet 1.0.1 1.0.1
Mailpoet_newsletters Mailpoet 2.5.4 2.5.4
Mailpoet_newsletters Mailpoet 0.9.2 0.9.2
Mailpoet_newsletters Mailpoet 2.3.1 2.3.1
Mailpoet_newsletters Mailpoet 2.4.1 2.4.1
Mailpoet_newsletters Mailpoet 2.3.2 2.3.2
Mailpoet_newsletters Mailpoet 2.6 2.6
Mailpoet_newsletters Mailpoet 2.5.9.3 2.5.9.3
Mailpoet_newsletters Mailpoet 2.0.7 2.0.7
Mailpoet_newsletters Mailpoet 2.0.8 2.0.8
Mailpoet_newsletters Mailpoet 2.0.9 2.0.9
Mailpoet_newsletters Mailpoet 2.4.4 2.4.4
Mailpoet_newsletters Mailpoet 2.6.4 2.6.4
Mailpoet_newsletters Mailpoet 2.5.3 2.5.3
Mailpoet_newsletters Mailpoet 2.3.3 2.3.3
Mailpoet_newsletters Mailpoet 2.0.5 2.0.5
Mailpoet_newsletters Mailpoet 2.0.1 2.0.1
Mailpoet_newsletters Mailpoet 2.2.1 2.2.1
Mailpoet_newsletters Mailpoet 2.0.2 2.0.2
Mailpoet_newsletters Mailpoet 1.0 1.0
Mailpoet_newsletters Mailpoet 0.9.1 0.9.1
Mailpoet_newsletters Mailpoet 2.1.3 2.1.3
Mailpoet_newsletters Mailpoet 2.5.9 2.5.9
Mailpoet_newsletters Mailpoet 2.5.9.4 2.5.9.4
Mailpoet_newsletters Mailpoet 2.5 2.5
Mailpoet_newsletters Mailpoet 2.1.5 2.1.5
Mailpoet_newsletters Mailpoet 2.6.5 2.6.5
Mailpoet_newsletters Mailpoet 1.1.4 1.1.4
Mailpoet_newsletters Mailpoet 2.2.3 2.2.3
Mailpoet_newsletters Mailpoet 2.5.8 2.5.8
Mailpoet_newsletters Mailpoet 2.6.8 2.6.8
Mailpoet_newsletters Mailpoet 1.1.2 1.1.2
Mailpoet_newsletters Mailpoet 2.6.1 2.6.1
Mailpoet_newsletters Mailpoet 2.3.4 2.3.4
Mailpoet_newsletters Mailpoet 2.1.8 2.1.8
Mailpoet_newsletters Mailpoet 2.3 2.3
Mailpoet_newsletters Mailpoet * 2.6.10
Mailpoet_newsletters Mailpoet 2.6.7 2.6.7
Mailpoet_newsletters Mailpoet 2.1.7 2.1.7
Mailpoet_newsletters Mailpoet 2.6 2.6
Mailpoet_newsletters Mailpoet 1.1.3 1.1.3
Mailpoet_newsletters Mailpoet 0.9 0.9
Mailpoet_newsletters Mailpoet 2.1.4 2.1.4
Mailpoet_newsletters Mailpoet 2.5.1 2.5.1
Mailpoet_newsletters Mailpoet 2.0.3 2.0.3
Mailpoet_newsletters Mailpoet 2.4.2 2.4.2
Mailpoet_newsletters Mailpoet 2.5.2 2.5.2
Mailpoet_newsletters Mailpoet 2.5.7 2.5.7
Mailpoet_newsletters Mailpoet 2.5.9.1 2.5.9.1
Mailpoet_newsletters Mailpoet 1.1.1 1.1.1
Mailpoet_newsletters Mailpoet 2.5.5 2.5.5
Mailpoet_newsletters Mailpoet 2.0.9.5 2.0.9.5
Mailpoet_newsletters Mailpoet 2.1.9 2.1.9
Mailpoet_newsletters Mailpoet 2.1.6 2.1.6
Mailpoet_newsletters Mailpoet 2.6.9 2.6.9
Mailpoet_newsletters Mailpoet 2.2.2 2.2.2
Mailpoet_newsletters Mailpoet 2.2 2.2
Mailpoet_newsletters Mailpoet 2.6.2 2.6.2
Mailpoet_newsletters Mailpoet 2.4 2.4
Mailpoet_newsletters Mailpoet 0.9.6 0.9.6
Mailpoet_newsletters Mailpoet 2.4.3 2.4.3
Mailpoet_newsletters Mailpoet 1.1 1.1
Mailpoet_newsletters Mailpoet 2.1 2.1
Mailpoet_newsletters Mailpoet 2.0.4 2.0.4
Mailpoet_newsletters Mailpoet 2.3.5 2.3.5
Mailpoet_newsletters Mailpoet 2.5.9.2 2.5.9.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]

References