WordPress 4.7.0 REST API class-wp-rest-users-controller.php information disclosure
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.1 | $0-$5k | 0.00 |
A vulnerability classified as problematic was found in WordPress 4.7.0 (Content Management System). Affected by this vulnerability is an unknown function of the file wp-includes/rest-api/endpoints/class-wp-rest-users-controller.php of the component REST API. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
wp-includes/rest-api/endpoints/class-wp-rest-users-controller.php in the REST API implementation in WordPress 4.7 before 4.7.1 does not properly restrict listings of post authors, which allows remote attackers to obtain sensitive information via a wp-json/wp/v2/users request.
The bug was discovered 01/11/2017. The weakness was disclosed 01/15/2017 by Dctor (oss-sec). It is possible to read the advisory at openwall.com. This vulnerability is known as CVE-2017-5487 since 01/14/2017. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
A public exploit has been developed by Dctor in PHP and been published 2 months after the advisory. It is possible to download the exploit at exploit-db.com. It is declared as functional. By approaching the search of inurl:wp-includes/rest-api/endpoints/class-wp-rest-users-controller.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 96606 (WordPress < 4.7.1 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CGI abuses and running in the context r. The commercial vulnerability scanner Qualys is able to test this issue with plugin 11772 (WordPress REST API User Enumeration Vulnerability). The code used by the exploit is:
header ('Content-type: text/html; charset=UTF-8'); $url= "https://bucaneiras.org/"; $payload="wp-json/wp/v2/users/"; $urli = file_get_contents($url.$payload); $json = json_decode($urli, true); if($json){ echo "*-----------------------------*\n"; foreach($json as $users){ echo "[*] ID : |" .$users['id'] ."|\n"; echo "[*] Name: |" .$users['name'] ."|\n"; echo "[*] User :|" .$users['slug'] ."|\n"; echo "\n"; }echo "*-----------------------------*";} else{echo "[*] No user";}
Upgrading to version 4.7.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (96606) and Exploit-DB (41497). The entries 95348, 95349, 95350 and 95351 are pretty similar.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 4.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Functional
Author: Dctor
Programming Language: 🔍
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Nessus ID: 96606
Nessus Name: WordPress < 4.7.1 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 100908
OpenVAS Name: WordPress json User Enumeration Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Upgrade: WordPress 4.7.1
Patch: github.com
Timeline
01/11/2017 🔍01/11/2017 🔍
01/11/2017 🔍
01/14/2017 🔍
01/14/2017 🔍
01/15/2017 🔍
01/15/2017 🔍
01/18/2017 🔍
03/03/2017 🔍
03/03/2017 🔍
10/28/2022 🔍
Sources
Product: wordpress.comAdvisory: daf358983cc1ce0c77bf6d2de2ebbb43df2add60
Researcher: Dctor
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2017-5487 (🔍)
SecurityTracker: 1037591
SecurityFocus: 95391 - WordPress Prior to 4.7.1 Information Disclosure Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 01/15/2017 10:40Updated: 10/28/2022 20:06
Changes: 01/15/2017 10:40 (88), 06/08/2020 09:18 (3), 10/28/2022 20:06 (5)
Complete: 🔍
Cache ID: 18:23D:103
No comments yet. Languages: en.
Please log in to comment.