CVE-2017-5493 json
wp-includes/ms-functions.php in the Multisite WordPress API in WordPress before 4.7.1 does not properly choose random numbers for keys, whi…
published 9y ago modified 4mo ago also EUVD-2017-14597
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- wordpress Debian 14, Debian 13, Debian 12 4.7.1+dfsg-1
debian advisories DEBIAN-CVE-2017-5493
- wordpress Arch Linux 4.7.1-1
arch linux advisories AVG-142
Is CVE-2017-5493 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.89% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
- Technology feeds
References
-
github.com
/WordPress/WordPress/commit/cea9e2dc62abf777e06b12ec4ad9d1aaa49b29f4
patch
-
debian.org
/security/2017/dsa-3779
vendor-advisory
-
codex.wordpress.org
/Version_4.7.1
release-notes, vendor-advisory
-
wordpress.org
/news/2017/01/wordpress-4-7-1-security-and-maintenance-release/
vendor-advisory
- wpvulndb.com /vulnerabilities/8721
-
securityfocus.com
/bid/95401
vdb-entry
-
openwall.com
/lists/oss-security/2017/01/14/6
mailing-list, third-party-advisory
-
securitytracker.com
/id/1037591
vdb-entry
Sources
- CVE List CVE-2017-5493
- NVD CVE-2017-5493
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.