WordPress 2.0.2/2.0.3/2.0.4 path traversal

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

Summaryinfo

A vulnerability was found in WordPress 2.0.2/2.0.3/2.0.4. It has been classified as problematic. This affects an unknown part. The manipulation leads to path traversal. This vulnerability is documented as CVE-2006-5705. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in WordPress 2.0.2/2.0.3/2.0.4 (Content Management System). It has been rated as problematic. This issue affects an unknown code block. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Multiple directory traversal vulnerabilities in plugins/wp-db-backup.php in WordPress before 2.0.5 allow remote authenticated users to read or overwrite arbitrary files via directory traversal sequences in the (1) backup and (2) fragment parameters in a GET request.

The bug was discovered 10/27/2006. The weakness was released 11/03/2006 (Website). The advisory is shared at gentoo.org. The identification of this vulnerability is CVE-2006-5705 since 11/03/2006. The attack may be initiated remotely. The requirement for exploitation is a simple authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 7 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 23675 (GLSA-200611-10 : WordPress: Multiple vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Gentoo Local Security Checks and running in the context l.

Upgrading to version 2.0.5 eliminates this vulnerability. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (30407), Tenable (23675), SecurityFocus (BID 20869†), OSVDB (40797†) and Secunia (SA22683†). Entries connected to this vulnerability are available at VDB-33356 and VDB-33355. 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.3
VulDB Meta Temp Score: 5.7

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

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Path traversal
CWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 23675
Nessus Name: GLSA-200611-10 : WordPress: Multiple vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 57923
OpenVAS Name: Gentoo Security Advisory GLSA 200611-10 (wordpress)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Upgrade: WordPress 2.0.5

Timelineinfo

10/27/2006 🔍
11/02/2006 +6 days 🔍
11/02/2006 +0 days 🔍
11/03/2006 +1 days 🔍
11/03/2006 +0 days 🔍
11/03/2006 +0 days 🔍
11/03/2006 +0 days 🔍
11/17/2006 +14 days 🔍
11/20/2006 +3 days 🔍
11/28/2006 +8 days 🔍
03/12/2015 +3026 days 🔍
04/26/2026 +4063 days 🔍

Sourcesinfo

Product: wordpress.com

Advisory: gentoo.org
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2006-5705 (🔍)
GCVE (CVE): GCVE-0-2006-5705
GCVE (VulDB): GCVE-100-33101
X-Force: 30407
SecurityFocus: 20869 - WordPress 2.04 Multiple Security Vulnerabilities
Secunia: 22683 - WordPress Multiple Vulnerabilities, Moderately Critical
OSVDB: 40797 - WordPress - Multiple Security Issues
Vulnerability Center: 13158 - WordPress Before 2.0.5 Directory Traversal Allows Remote Attackers to Read Arbitrary Files, Medium
Vupen: ADV-2006-4307

See also: 🔍

Entryinfo

Created: 03/12/2015 22:21
Updated: 04/26/2026 08:36
Changes: 03/12/2015 22:21 (80), 07/11/2019 09:20 (4), 04/26/2026 08:36 (19)
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 ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!