Radar sectionsDatabase
Check my site
WordPress wordpress core

WordPress Core < 4.7.1 — Weak Multi-Site Activation Key for User and Site Signup

CVE-2017-5493Published · Updated

Action summary

Affected: ≤4.7.0Update to 3.7.17 or 3.8.17 or 3.9.15 or 4.0.14 or 4.1.14 or 4.2.11 or 4.3.7 or 4.4.6 or 4.5.5 or 4.6.2 or 4.7.1 or newer

Fixed versions are per release branch: update to the fix for the branch you run.

All remediation steps
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:L Confidentiality
Low
I:N Integrity
None
A:N Availability
None
Weakness
CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

WordPress wordpress

  1. Affected≤ 4.7.0
  2. Patched in3.7.17 / 3.8.17 / 3.9.15 / 4.0.14 / 4.1.14 / 4.2.11 / 4.3.7 / 4.4.6 / 4.5.5 / 4.6.2 / 4.7.1

Update to 3.7.17 / 3.8.17 / 3.9.15 / 4.0.14 / 4.1.14 / 4.2.11 / 4.3.7 / 4.4.6 / 4.5.5 / 4.6.2 / 4.7.1 or newer.

You are affected if you run ≤ 4.7.0. Version 3.7.17, 3.8.17, 3.9.15, 4.0.14, 4.1.14, 4.2.11, 4.3.7, 4.4.6, 4.5.5, 4.6.2, 4.7.1 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WordPress.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to one of the following versions, or a newer patched version: 3.7.17, 3.8.17, 3.9.15, 4.0.14, 4.1.14, 4.2.11, 4.3.7, 4.4.6, 4.5.5, 4.6.2, 4.7.1
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch WordPress to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Jack.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?