WordPress up to 4.7.2 Press This class-wp-press-this.php cross-site request forgery

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

Summaryinfo

A vulnerability marked as problematic has been reported in WordPress up to 4.7.2. Affected by this issue is some unknown functionality of the file wp-admin/includes/class-wp-press-this.php of the component Press This. Performing a manipulation results in cross-site request forgery. This vulnerability is reported as CVE-2017-6819. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in WordPress up to 4.7.2 (Content Management System). This affects an unknown code of the file wp-admin/includes/class-wp-press-this.php of the component Press This. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. The summary by CVE is:

In WordPress before 4.7.3, there is cross-site request forgery (CSRF) in Press This (wp-admin/includes/class-wp-press-this.php), leading to excessive use of server resources. The CSRF can trigger an outbound HTTP request for a large file that is then parsed by Press This.

The bug was discovered 03/07/2017. The weakness was disclosed 03/12/2017 by Sipke Mellema (oss-sec). The advisory is shared at openwall.com. This vulnerability is uniquely identified as CVE-2017-6819 since 03/11/2017. 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 are known, but no exploit is available.

By approaching the search of inurl:wp-admin/includes/class-wp-press-this.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 97635 (WordPress < 4.7.3 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 11769 (WordPress Prior to 4.7.3 Multiple Security Vulnerabilities).

Upgrading to version 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 even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (97635), SecurityFocus (BID 96602†) and SecurityTracker (ID 1037959†). Further details are available at hackerone.com. The entries VDB-97852, VDB-97853, VDB-97854 and VDB-97855 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.3

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.5
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Cross-site request forgery
CWE: CWE-352 / CWE-862 / CWE-863
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: 97635
Nessus Name: WordPress < 4.7.3 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 803448
OpenVAS Name: WordPress Multiple Vulnerabilities Mar17 (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.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/07/2017 +0 days 🔍
03/09/2017 +2 days 🔍
03/11/2017 +2 days 🔍
03/11/2017 +0 days 🔍
03/12/2017 +1 days 🔍
03/12/2017 +0 days 🔍
12/25/2024 +2845 days 🔍

Sourcesinfo

Product: wordpress.com

Advisory: openwall.com
Researcher: Sipke Mellema
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-6819 (🔍)
GCVE (CVE): GCVE-0-2017-6819
GCVE (VulDB): GCVE-100-97857
SecurityFocus: 96602 - WordPress Prior to 4.7.3 Cross Site Request Forgery Vulnerability
SecurityTracker: 1037959

Misc.: 🔍
See also: 🔍

Entryinfo

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

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!