dicshunary 0.1 Alpha check_status.php dicshunary_root_path file inclusion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in dicshunary 0.1 Alpha and classified as critical. Affected by this issue is some unknown functionality of the file check_status.php. The manipulation of the argument dicshunary_root_path leads to file inclusion. This vulnerability is uniquely identified as CVE-2006-6281. Moreover, an exploit is present.
Details
A vulnerability, which was classified as critical, has been found in dicshunary 0.1 Alpha. This issue affects an unknown part of the file check_status.php. The manipulation of the argument dicshunary_root_path with an unknown input leads to a file inclusion vulnerability. Using CWE to declare the problem leads to CWE-73. The product allows user input to control or influence paths or file names that are used in filesystem operations. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
PHP remote file inclusion vulnerability in check_status.php in dicshunary 0.1 alpha allows remote attackers to execute arbitrary PHP code via a URL in the dicshunary_root_path parameter.
The weakness was disclosed 12/04/2006 as not defined posting (Bugtraq). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2006-6281 since 12/03/2006. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known.
A public exploit has been developed in Perl. The exploit is available at securityfocus.com. It is declared as proof-of-concept. By approaching the search of inurl:check_status.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 (30403), Exploit-DB (2808) and SecurityFocus (BID 21162†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: File inclusionCWE: CWE-73
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Programming Language: 🔍
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/17/2006 🔍12/03/2006 🔍
12/04/2006 🔍
12/04/2006 🔍
03/12/2015 🔍
09/26/2025 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2006-6281 (🔍)
GCVE (CVE): GCVE-0-2006-6281
GCVE (VulDB): GCVE-100-33617
X-Force: 30403 - Dicshunary check_status.php file include
SecurityFocus: 21162 - Dicshunary Check_Status.PHP Remote File Include Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/12/2015 22:21Updated: 09/26/2025 08:03
Changes: 03/12/2015 22:21 (51), 08/09/2018 07:34 (7), 09/26/2025 08:03 (22)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.