WordPress up to 4.7.2 Control Character pluggable.php input validation

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.0$0-$5k0.00

Summaryinfo

A vulnerability was found in WordPress. It has been rated as problematic. This affects an unknown function of the file wp-includes/pluggable.php of the component Control Character Handler. The manipulation leads to input validation. This vulnerability is listed as CVE-2017-6815. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in WordPress (Content Management System) and classified as critical. This issue affects an unknown function of the file wp-includes/pluggable.php of the component Control Character Handler. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In WordPress before 4.7.3 (wp-includes/pluggable.php), control characters can trick redirect URL validation.

The bug was discovered 03/07/2017. The weakness was presented 03/12/2017 (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2017-6815 since 03/11/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $5k-$25k. By approaching the search of inurl:wp-includes/pluggable.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 97797 (Debian DLA-860-1 : wordpress security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 175994 (Debian Security Update for wordpress (DSA 3815-1)).

Upgrading to version 3.7.19, 3.8.19, 3.9.17, 4.0.16, 4.1.16, 4.2.13, 4.3.9, 4.4.8, 4.5.7, 4.6.4 or 4.7.3 eliminates this vulnerability. The upgrade is hosted for download at github.com. A possible mitigation has been published 5 days after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (97797), SecurityFocus (BID 96600†) and SecurityTracker (ID 1037959†). See VDB-97852, VDB-97854, VDB-97855 and VDB-97856 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.2
VulDB Meta Temp Score: 6.0

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

NVD Base Score: 6.1
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Input validation
CWE: CWE-20
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: 97797
Nessus Name: Debian DLA-860-1 : wordpress security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 703815
OpenVAS Name: Debian Security Advisory DSA 3815-1 (wordpress - security update)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: WordPress 3.7.19/3.8.19/3.9.17/4.0.16/4.1.16/4.2.13/4.3.9/4.4.8/4.5.7/4.6.4/4.7.3

Timelineinfo

03/06/2017 🔍
03/07/2017 +1 days 🔍
03/11/2017 +4 days 🔍
03/11/2017 +0 days 🔍
03/12/2017 +1 days 🔍
03/12/2017 +0 days 🔍
03/17/2017 +5 days 🔍
03/20/2017 +3 days 🔍
12/25/2024 +2837 days 🔍

Sourcesinfo

Product: wordpress.com

Advisory: securityfocus.com⛔
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-6815 (🔍)
GCVE (CVE): GCVE-0-2017-6815
GCVE (VulDB): GCVE-100-97853

OVAL: 🔍

SecurityFocus: 96600 - WordPress Prior to 4.7.3 URL Redirection Vulnerability
SecurityTracker: 1037959

See also: 🔍

Entryinfo

Created: 03/12/2017 08:33
Updated: 12/25/2024 21:11
Changes: 03/12/2017 08:33 (83), 06/08/2020 07:49 (2), 12/25/2024 21:11 (17)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!