WordPress through 4.8.2 uses a weak MD5-based password hashing algorithm, which makes it easier for attackers to determine cleartext values by leveraging access to the hash values. NOTE: the approach to changing this may not be fully compatible with certain use cases, such as migration of a WordPress site from a web host that uses a recent PHP version to a different web host that uses PHP 5.2. These use cases are plausible (but very unlikely) based on statistics showing widespread deployment of WordPress with obsolete PHP versions.
This is a vulnerability exploitable with network access which means the vulnerable software is bound to
the network stack and the attacker does not require local network access or local access to exploit it.
Such a vulnerability is often termed “remotely exploitable”.
Specialized access conditions or extenuating circumstances do not exist. The following are examples:
The affected product typically requires access to a wide range of systems and users, possibly anonymous an untrusted (e.g., Internet-facing web or mail server).
The affected configuration is default or ubiquitous. The attack can be performed manually and requires little skill or additional information gathering.
The 'race condition' is a lazy one (i.e., it is technically a race but easily winnable).
Authentication is not required to access and exploit the vulnerability.
There is considerable informational disclosure. Access to some system files is
possible, but the attacker does not have control over what is obtained, or the scope of
the loss is constrained. An example is a vulnerability that divulges only certain tables
in a database.
There is no impact to the integrity of the system.
There is no impact to the availability of the system.
NIST (National Institute of Standards and Technology) NVD (National Vulnerability Database)