CVE-2014-5204: CSRF
First published: Mon Aug 18 2014(Updated: )
wp-includes/pluggable.php in WordPress before 3.9.2 rejects invalid CSRF nonces with a different timing depending on which characters in the nonce are incorrect, which makes it easier for remote attackers to bypass a CSRF protection mechanism via a brute-force attack.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Debian GNU/Linux | =7.0 | |
| WordPress | <=3.9.1 | |
| WordPress | =3.9.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2014-5204?
CVE-2014-5204 is considered a high severity vulnerability that allows remote attackers to bypass CSRF protections.
How do I fix CVE-2014-5204?
To fix CVE-2014-5204, update WordPress to version 3.9.2 or later.
Which versions of WordPress are affected by CVE-2014-5204?
WordPress versions prior to 3.9.2, including 3.9.0 and 3.9.1, are affected by CVE-2014-5204.
Can CVE-2014-5204 be exploited remotely?
Yes, CVE-2014-5204 can be exploited remotely, allowing attackers to bypass CSRF protections.
What type of attack does CVE-2014-5204 facilitate?
CVE-2014-5204 facilitates a brute-force attack against the CSRF protection mechanism.
- agent/references
- agent/type
- agent/author
- agent/severity
- agent/remedy
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/weakness
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/debian
- canonical/debian gnu/linux
- version/debian gnu/linux/7.0
- vendor/wordpress
- canonical/wordpress
- version/wordpress/3.9.1
- version/wordpress/3.9.0