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

Summaryinfo

A vulnerability was found in WordPress 4.5.3. It has been classified as problematic. This vulnerability affects unknown code. This manipulation causes cross-site request forgery. This vulnerability is tracked as CVE-2016-6897. The attack is possible to be carried out remotely. Moreover, an exploit is present. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in WordPress 4.5.3 (Content Management System). It has been declared as critical. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was disclosed 08/22/2016 by Yorick Koster as Path traversal vulnerability in WordPress Core Ajax handlers as confirmed advisory (Website). It is possible to read the advisory at sumofpwn.nl. This vulnerability is known as CVE-2016-6897 since 08/22/2016. The attack can be launched remotely. The requirement for exploitation is a single authentication. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available.

It is possible to download the exploit at exploit-db.com. It is declared as highly functional. The vulnerability scanner Nessus provides a plugin with the ID 93111 (WordPress < 4.6 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 276130 (Fedora Security Update for wordpress (FEDORA-2016-80a1d6211a)).

Upgrading to version 4.6.0 eliminates this vulnerability. The upgrade is hosted for download at codex.wordpress.org. 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 Exploit-DB (40288), Tenable (93111), SecurityFocus (BID 92572†) and SecurityTracker (ID 1036683†). The entries VDB-90906 and VDB-95467 are pretty similar. 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.5
VulDB Meta Temp Score: 6.3

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
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: 🔍
Access: Public
Status: Highly functional
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 93111
Nessus Name: WordPress < 4.6 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 64581
OpenVAS Name: Fedora Update for wordpress FEDORA-2016-91bfe9ddb8
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

MetaSploit ID: wordpress_directory_traversal_dos.rb
MetaSploit Name: WordPress Traversal Directory DoS
MetaSploit File: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: WordPress 4.6.0
Patch: github.com

Timelineinfo

08/16/2016 🔍
08/20/2016 +4 days 🔍
08/22/2016 +2 days 🔍
08/22/2016 +0 days 🔍
08/22/2016 +0 days 🔍
08/23/2016 +1 days 🔍
08/25/2016 +2 days 🔍
01/18/2017 +146 days 🔍
05/13/2026 +3402 days 🔍

Sourcesinfo

Product: wordpress.com

Advisory: Path traversal vulnerability in WordPress Core Ajax handlers
Researcher: Yorick Koster
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-6897 (🔍)
GCVE (CVE): GCVE-0-2016-6897
GCVE (VulDB): GCVE-100-90907
SecurityFocus: 92572 - WordPress CVE-2016-6897 Cross Site Request Forgery Vulnerability
SecurityTracker: 1036683

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 08/23/2016 11:19
Updated: 05/13/2026 18:43
Changes: 08/23/2016 11:19 (76), 05/08/2019 12:57 (14), 09/14/2022 09:34 (5), 08/31/2024 20:36 (14), 05/13/2026 18:43 (1)
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 ▸

Want to know what is going to be exploited?

We predict KEV entries!