bugtraq - WordPress <=v4.4 Username Exists Information Disclosure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date: Thu, 10 Dec 2015 03:51:13 -0500
From: "John SECURELI.com" <john@...ureli.com>
To: bugtraq@...urityfocus.com
Subject: WordPress <=v4.4 Username Exists Information Disclosure

Information security research credited to John Martinelli @ 
SECURELI.com. (john@...ureli.com)

-----

Affects: WordPress <=v4.4
Vulnerability: Information Disclosure
CVE-ID: Pending
Impact: Username exists disclosure on /wp-login.php

-----

By default, WordPress <=4.4 discloses whether a username is registered 
inside the system, allowing attackers the opportunity to do brute-force 
password cracking attacks.

One proof of concept would be to scrape Alexa.com for WordPress running 
domains, check automatically whether it confirms the username (possibly 
top 100 most popular WP usernames) exists in the WordPress users table 
using a simple RegEx boolean to determine “IF USER EXISTS”, then to send 
a Selenium automated browser to attempt logins with top 10 most popular 
passwords.

Would easily allow attackers to login and with publishing or editing 
permissions, install malware onto the WordPress installation as well as 
potentially escalate privileges on the hosting account if running 
vulnerable versions of WordPress or plugins.

**** Proof screenshot @ 
http://secureli.com/information-security-research/wordpress/ ****