PHPX up to 3.2.6 Error Message forums.php limit information disclosure

Summaryinfo

A vulnerability has been found in PHPX and classified as problematic. This vulnerability affects unknown code of the file forums.php of the component Error Message Handler. This manipulation of the argument limit causes information disclosure. This vulnerability is tracked as CVE-2004-2362. Moreover, an exploit is present.

Detailsinfo

A vulnerability classified as problematic was found in PHPX (Content Management System). Affected by this vulnerability is an unknown part of the file forums.php of the component Error Message Handler. The manipulation of the argument limit with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

PHPX 3.2.6 and earlier allows remote attackers to obtain the physical path of PHPX via a null or invalid value in the limit parameter, which leaks the pathname in a database error message, as demonstrated using forums.php.

The weakness was disclosed 05/04/2004 by JeiAr (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2004-2362 since 08/16/2005. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a exploit are known. MITRE ATT&CK project uses the attack technique T1592 for this issue.

After before and not just, there has been an exploit disclosed. It is declared as proof-of-concept. By approaching the search of inurl:forums.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 (16064), OSVDB (5906†), Secunia (SA11554†) and SecurityTracker (ID 1010061†). The entries VDB-23259, VDB-23258, VDB-82009 and VDB-82010 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Content Management System

Name

• PHPX

Version

• 1.0.7
• 1.0.10
• 1.0.14
• 2.1.0
• 2.2.0
• 2.2.1
• 2.2.3
• 2.2.4
• 3.0.0
• 3.0.1
• 3.0.2
• 3.0.3
• 3.0.4
• 3.0.5
• 3.0.6
• 3.0.7
• 3.1.0
• 3.1.1
• 3.1.2
• 3.1.3
• 3.1.4
• 3.2.0
• 3.2.1
• 3.2.2
• 3.2.3
• 3.2.4
• 3.2.5
• 3.2.6

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion