CVE-2018-20151 json
In WordPress before 4.9.9 and 5.x before 5.0.1, the user-activation page could be read by a search engine's web crawler if an unusual confi…
published 2018-12-14 7 y ago modified 2026-06-17 4 mo ago also EUVD-2018-12720
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.8%
- EPSS 5.8% chance of exploitation in 30 days, percentile 93%
- public exploits
- 0
- none known
Summary
In WordPress before 4.9.9 and 5.x before 5.0.1, the user-activation page could be read by a search engine's web crawler if an unusual configuration were chosen. The search engine could then index and display a user's e-mail address and (rarely) the password that was generated by default.
Patch / fix
- wordpress wordpress 4.9.9, 5.0.1
- wordpress Debian 14, Debian 13, Debian 12 5.0.1+dfsg1-1
debian advisories DEBIAN-CVE-2018-20151
Exploit prediction
5.78% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).
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:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
-
debian.org
/security/2019/dsa-4401
vendor-advisory, third-party-advisory
-
wordpress.org
/support/wordpress-version/version-5-0-1/
release-notes, vendor-advisory
-
wpvulndb.com
/vulnerabilities/9174
vendor-advisory
-
codex.wordpress.org
/Version_4.9.9
product, vendor-advisory
-
wordpress.org
/news/2018/12/wordpress-5-0-1-security-release/
release-notes, vendor-advisory
-
securityfocus.com
/bid/106220
vdb-entry, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2019/02/msg00019.html
mailing-list, third-party-advisory
-
zdnet.com
/article/wordpress-plugs-bug-that-led-to-google-indexing-some-user-passwords/
press/media-coverage, third-party-advisory
Sources
- CVE List CVE-2018-20151
- NVD CVE-2018-20151
Fencer Vulns 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.