Plaino Wimpy MP3 up to 5.2 wimpy_trackplays.php

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

Summaryinfo

A vulnerability was found in Plaino Wimpy MP3 up to 5.2. It has been declared as problematic. The affected element is an unknown function of the file wimpy_trackplays.php. Executing a manipulation can lead to an unknown weakness. The identification of this vulnerability is CVE-2006-0787. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability has been found in Plaino Wimpy MP3 up to 5.2 and classified as problematic. This vulnerability affects some unknown processing of the file wimpy_trackplays.php. As an impact it is known to affect integrity, and availability. CVE summarizes:

wimpy_trackplays.php in Plaino Wimpy MP3 Player, possibly 5.2 and earlier, allows remote attackers to insert arbitrary strings into trackme.txt via the (1) trackFile, (2) trackArtist, and (3) trackTitle parameters, which can result in providing false information about songs, occupying excessive disk space with very long parameter values, and storing executable code that might be invoked through a different vulnerability. NOTE: since this issue, as described by the original researcher, is entirely dependent on the presence of another vulnerability, it could be argued that Wimpy cannot be responsible for how its data file is processed by applications outside of its control. Since this issue might only be useful as a facilitator manipulation in another vulnerability, perhaps it should not be included in CVE.

The weakness was shared 02/19/2006 by ReZEN (Website). The advisory is shared for download at xorcrew.net. This vulnerability was named CVE-2006-0787 since 02/19/2006. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:wimpy_trackplays.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at X-Force (24770), Exploit-DB (27244), SecurityFocus (BID 16696†) and Secunia (SA18900†). Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.8
VulDB Meta Temp Score: 4.4

VulDB Base Score: 4.8
VulDB Temp Score: 4.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Unknown
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

02/16/2006 🔍
02/16/2006 +0 days 🔍
02/19/2006 +3 days 🔍
02/19/2006 +0 days 🔍
02/19/2006 +0 days 🔍
03/12/2015 +3308 days 🔍
03/13/2025 +3654 days 🔍

Sourcesinfo

Advisory: xorcrew.net
Researcher: ReZEN
Status: Not defined

CVE: CVE-2006-0787 (🔍)
GCVE (CVE): GCVE-0-2006-0787
GCVE (VulDB): GCVE-100-28804
X-Force: 24770 - Wimpy MP3 Player wimpy_trackplays.php no authentication
SecurityFocus: 16696 - Wimpy MP3 Player Text File Overwrite Weakness
Secunia: 18900 - Wimpy MP3 Player trackme.txt File Modification Weakness, Not Critical

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

Entryinfo

Created: 03/12/2015 11:11
Updated: 03/13/2025 16:29
Changes: 03/12/2015 11:11 (50), 08/01/2017 08:05 (6), 03/13/2025 16:29 (25)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source 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!