phpCMS 1.1.9/1.2.0/1.2.1 Installation parser.php File information disclosure

Summaryinfo

A vulnerability has been found in phpCMS 1.1.9/1.2.0/1.2.1 and classified as problematic. This impacts an unknown function of the file parser.php of the component Installation. The manipulation of the argument File leads to information disclosure. This vulnerability is uniquely identified as CVE-2004-1203. No exploit exists.

Detailsinfo

A vulnerability was found in phpCMS 1.1.9/1.2.0/1.2.1 and classified as problematic. This issue affects an unknown part of the file parser.php of the component Installation. The manipulation of the argument file with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

parser.php in phpCMS 1.2.1 and earlier, with non-stealth and debug modes enabled, allows remote attackers to gain sensitive information via an invalid file parameter, which reveals the web server s installation path.

The weakness was disclosed 01/10/2005 as not defined posting (Bugtraq). It is possible to read the advisory at marc.theaimsgroup.com. The identification of this vulnerability is CVE-2004-1203 since 12/14/2004. 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 of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

By approaching the search of inurl:parser.php it is possible to find vulnerable targets with Google Hacking. The commercial vulnerability scanner Qualys is able to test this issue with plugin 11606 (phpCMS parser.php Information Disclosure Vulnerability).

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 (18272) and Vulnerability Center (SBV-29286†). The entry VDB-23746 is pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• phpCMS

Version

• 1.1.9
• 1.2.0
• 1.2.1

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion