WordPress security changelog
HIGH CVE-2017-5493 Deferred

WordPress component: A security weakness

WordPress component is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 7.5 CVSS · cve@mitre.org
NVD score 7.5 CVSS 3.0 · nvd@nist.gov
Component
WordPress component
Plugin slug
Not applicable
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Jan 15, 2017
Weakness
CWE-338 — Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
What to do

Update, patch or deactivate.

Update WordPress component to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

wp-includes/ms-functions.php in the Multisite WordPress API in WordPress before 4.7.1 does not properly choose random numbers for keys, which makes it easier for remote attackers to bypass intended access restrictions via a crafted (1) site signup or (2) user signup.

NVD vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

References

Primary and upstream sources