WordPress up to 2.3.2 Whitelist 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.
5.2$0-$5k0.00

Summaryinfo

A vulnerability was found in WordPress up to 2.3.2. It has been rated as problematic. This affects an unknown function of the component Whitelist. Performing a manipulation results in access control. This vulnerability is cataloged as CVE-2010-5293. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in WordPress up to 2.3.2 (Content Management System). It has been classified as problematic. This affects an unknown function of the component Whitelist. 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, and integrity. The summary by CVE is:

wp-includes/comment.php in WordPress before 3.0.2 does not properly whitelist trackbacks and pingbacks in the blogroll, which allows remote attackers to bypass intended spam restrictions via a crafted URL, as demonstrated by a URL that triggers a substring match.

The weakness was shared 01/20/2014 (Website). The advisory is shared at core.trac.wordpress.org. This vulnerability is uniquely identified as CVE-2010-5293 since 01/20/2014. 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. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 51860 (WordPress < 3.0.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.

Upgrading to version 2.3.3 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 X-Force (95712), Tenable (51860), SecurityFocus (BID 65235†) and Vulnerability Center (SBV-55694†). The entries VDB-66132, VDB-66131 and VDB-66130 are related to this item. 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.2

VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

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

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 51860
Nessus Name: WordPress < 3.0.2 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: WordPress 2.3.3

Timelineinfo

11/30/2010 🔍
11/30/2010 +0 days 🔍
11/30/2010 +0 days 🔍
02/03/2011 +65 days 🔍
01/20/2014 +1082 days 🔍
01/20/2014 +0 days 🔍
01/20/2014 +0 days 🔍
03/24/2015 +428 days 🔍
01/13/2016 +295 days 🔍
01/31/2022 +2210 days 🔍

Sourcesinfo

Product: wordpress.com

Advisory: 16373
Status: Not defined
Confirmation: 🔍

CVE: CVE-2010-5293 (🔍)
GCVE (CVE): GCVE-0-2010-5293
GCVE (VulDB): GCVE-100-66129
X-Force: 95712
SecurityFocus: 65235 - WordPress Remote Security Bypass Vulnerability
Secunia: 42431
Vulnerability Center: 55694 - WordPress before 3.0.2 Remote Security Bypass via a Crafted URL, Medium

See also: 🔍

Entryinfo

Created: 03/24/2015 15:54
Updated: 01/31/2022 13:34
Changes: 03/24/2015 15:54 (54), 06/21/2018 09:01 (15), 01/31/2022 13:28 (3), 01/31/2022 13:34 (2)
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.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!