PHP Heaven phpMyChat 0.14.5 Installation setup.php3 access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in PHP Heaven phpMyChat 0.14.5. Affected by this issue is some unknown functionality of the file setup.php3 of the component Installation. The manipulation leads to access control. This vulnerability is referenced as CVE-2004-2718. Furthermore, an exploit is available.
Details
A vulnerability was found in PHP Heaven phpMyChat 0.14.5 (Programming Language Software) and classified as problematic. This issue affects some unknown functionality of the file setup.php3 of the component Installation. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality. The summary by CVE is:
PHPMyChat 0.14.5 does not remove or protect setup.php3 after installation, which allows attackers to obtain sensitive information including database passwords via a direct request.
The weakness was published 12/22/2004 (Website). The advisory is shared at securiteam.com. The identification of this vulnerability is CVE-2004-2718 since 10/06/2007. 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. MITRE ATT&CK project uses the attack technique T1068 for this issue.
After immediately, there has been an exploit disclosed. The exploit is available at exploit-db.com. It is declared as proof-of-concept.
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 Exploit-DB (703), OSVDB (44922†) and Secunia (SA11894†). Similar entries are available at VDB-23584, VDB-23583 and VDB-23582. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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: 🔍
Exploit Delay Time: 🔍
Timeline
06/18/2004 🔍12/22/2004 🔍
12/22/2004 🔍
12/31/2004 🔍
10/06/2007 🔍
05/10/2008 🔍
03/10/2015 🔍
05/29/2025 🔍
Sources
Advisory: securiteam.com⛔Status: Not defined
CVE: CVE-2004-2718 (🔍)
GCVE (CVE): GCVE-0-2004-2718
GCVE (VulDB): GCVE-100-23585
Secunia: 11894 - phpMyChat Multiple Vulnerabilities, Moderately Critical
OSVDB: 44922 - PHPMyChat setup.php3 Direct Request Remote Information Disclosure
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/10/2015 12:14Updated: 05/29/2025 19:11
Changes: 03/10/2015 12:14 (51), 06/30/2018 09:17 (7), 05/29/2025 19:11 (23)
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.