WordPress up to 4.2.3 Widget Title 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.
4.1$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in WordPress up to 4.2.3. This affects an unknown function of the component Widget Title Handler. The manipulation leads to cross-site request forgery. This vulnerability is documented as CVE-2015-5731. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in WordPress up to 4.2.3 (Content Management System). It has been rated as problematic. This issue affects an unknown functionality of the component Widget Title Handler. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity.

The weakness was released 08/04/2015 as WordPress 4.2.4 Security and Maintenance Release as confirmed release notes (Website). It is possible to read the advisory at wordpress.org. The identification of this vulnerability is CVE-2015-5731 since 03/05/2015. 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. The technical details are unknown and an exploit is not publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 85546 (Debian DLA-294-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 11552 (WordPress Prior to 4.2.4 Multiple Security Vulnerabilities).

Upgrading to version 4.2.4 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability. The release notes contains the following remark:

This release addresses six issues, including three cross-site scripting vulnerabilities and a potential SQL injection that could be used to compromise a site (...)

The vulnerability is also documented in the databases at Tenable (85546), SecurityFocus (BID 76160†), SecurityTracker (ID 1033178†) and Vulnerability Center (SBV-54649†). codex.wordpress.org is providing further details. Entries connected to this vulnerability are available at VDB-76800, VDB-76929, VDB-76934 and VDB-76933. 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: 4.3
VulDB Meta Temp Score: 4.1

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

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

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 85546
Nessus Name: Debian DLA-294-1 : wordpress security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 703332
OpenVAS Name: Debian Security Advisory DSA 3332-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 4.2.4

Timelineinfo

03/05/2015 🔍
08/03/2015 +151 days 🔍
08/04/2015 +1 days 🔍
08/04/2015 +0 days 🔍
08/04/2015 +0 days 🔍
08/07/2015 +3 days 🔍
08/20/2015 +13 days 🔍
11/09/2015 +81 days 🔍
11/27/2015 +18 days 🔍
06/07/2022 +2384 days 🔍

Sourcesinfo

Product: wordpress.com

Advisory: WordPress 4.2.4 Security and Maintenance Release
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2015-5731 (🔍)
GCVE (CVE): GCVE-0-2015-5731
GCVE (VulDB): GCVE-100-76931

OVAL: 🔍

SecurityFocus: 76160
SecurityTracker: 1033178
Vulnerability Center: 54649 - WordPress before 4.2.4 Remote Session Hijacking, CSRF and DoS Vulnerabilities via a Get-Post-Lock Action, Medium

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 08/07/2015 10:11
Updated: 06/07/2022 12:56
Changes: 08/07/2015 10:11 (73), 05/08/2018 09:12 (7), 06/07/2022 12:56 (3)
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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!