First published: Tue Oct 03 2017(Updated: )
WordPress 4.8.2 stores cleartext wp_signups.activation_key values (but stores the analogous wp_users.user_activation_key values as hashes), which might make it easier for remote attackers to hijack unactivated user accounts by leveraging database read access (such as access gained through an unspecified SQL injection vulnerability).
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/wordpress | 5.0.15+dfsg1-0+deb10u1 5.0.19+dfsg1-0+deb10u1 5.7.8+dfsg1-0+deb11u2 6.1.1+dfsg1-1 6.3.1+dfsg1-1 | |
WordPress | =4.8.2 | |
Debian GNU/Linux | =8.0 | |
Debian GNU/Linux | =9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-14990 has a moderate severity level due to the potential for user account hijacking.
To fix CVE-2017-14990, upgrade your WordPress installation to a version later than 4.8.2 where the issue is resolved.
CVE-2017-14990 specifically affects WordPress version 4.8.2.
The primary risk associated with CVE-2017-14990 is that attackers could hijack unactivated user accounts if they gain database read access.
CVE-2017-14990 is not specific to any operating system but affects WordPress installations running on Debian systems as well.