WordPress up to 4.7.1 class-wp-rest-posts-controller.php register_routes access control

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.7$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in WordPress up to 4.7.1. Affected by this issue is the function register_routes of the file wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php. Performing a manipulation results in access control. This vulnerability was named CVE-2017-1001000. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in WordPress up to 4.7.1 (Content Management System). This affects the function register_routes of the file wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

The register_routes function in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in the REST API in WordPress 4.7.x before 4.7.2 does not require an integer identifier, which allows remote attackers to modify arbitrary pages via a request for wp-json/wp/v2/posts followed by a numeric value and a non-numeric value, as demonstrated by the wp-json/wp/v2/posts/123?id=123helloworld URI.

The bug was discovered 02/10/2017. The weakness was presented 04/03/2017 by Security Team with WordPress Security Team (oss-sec). It is possible to read the advisory at openwall.com. This vulnerability is uniquely identified as CVE-2017-1001000 since 04/02/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

By approaching the search of inurl:wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 96906 (WordPress < 4.7.2 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 11758 (WordPress Prior to 4.7.2 Multiple Security Vulnerabilities).

Upgrading to version 4.7.2 eliminates this vulnerability. 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 (96906) and SecurityFocus (BID 95816†). See VDB-96275, VDB-96276 and VDB-96277 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.9
VulDB Meta Temp Score: 6.7

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 96906
Nessus Name: WordPress < 4.7.2 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 803448
OpenVAS Name: WordPress < 4.7.2 Multiple Security Vulnerabilities (Windows)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: WordPress 4.7.2
Patch: github.com

Timelineinfo

01/26/2017 🔍
01/26/2017 +0 days 🔍
01/31/2017 +5 days 🔍
02/10/2017 +10 days 🔍
04/02/2017 +51 days 🔍
04/02/2017 +0 days 🔍
04/03/2017 +1 days 🔍
04/03/2017 +0 days 🔍
11/24/2022 +2061 days 🔍

Sourcesinfo

Product: wordpress.com

Advisory: e357195ce303017d517aff944644a7a1232926f7
Researcher: Security Team
Organization: WordPress Security Team
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-1001000 (🔍)
GCVE (CVE): GCVE-0-2017-1001000
GCVE (VulDB): GCVE-100-99243
SecurityFocus: 95816 - WordPress Prior to 4.7.2 Multiple Security Vulnerabilities
OSVDB: - WordPress register_routes function security bypass
SecurityTracker: 1037731

See also: 🔍

Entryinfo

Created: 04/03/2017 16:57
Updated: 11/24/2022 17:42
Changes: 04/03/2017 16:57 (78), 08/25/2020 12:01 (4), 11/24/2022 17:42 (6)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!