WHMCS WHMCompleteSolution up to 4.5.2 submitticket.php report path traversal

Summaryinfo

A vulnerability identified as problematic has been detected in WHMCS WHMCompleteSolution. This affects an unknown part of the file submitticket.php. This manipulation of the argument report causes path traversal. This vulnerability is tracked as CVE-2011-4810. Moreover, an exploit is present.

Detailsinfo

A vulnerability was found in WHMCS WHMCompleteSolution. It has been declared as problematic. Affected by this vulnerability is some unknown functionality of the file submitticket.php. The manipulation of the argument report with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect confidentiality. The summary by CVE is:

Multiple directory traversal vulnerabilities in WHMCompleteSolution (WHMCS) 3.x and 4.x allow remote attackers to read arbitrary files via the templatefile parameter to (1) submitticket.php and (2) downloads.php, and (3) the report parameter to admin/reports.php.

The weakness was disclosed 12/13/2011 (Website). The advisory is shared at exploit-db.com. This vulnerability is known as CVE-2011-4810 since 12/13/2011. 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 public exploit are known. MITRE ATT&CK project uses the attack technique T1006 for this issue.

It is possible to download the exploit at exploit-db.com. It is declared as highly functional. By approaching the search of inurl:submitticket.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 vulnerability database at OSVDB (77754†). The entry VDB-59680 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• WHMCS

Name

• WHMCompleteSolution

Version

• 3.0.0
• 4.0.0
• 4.0.1
• 4.0.2
• 4.1.0
• 4.1.1
• 4.1.2
• 4.2.0
• 4.2.1
• 4.3.0
• 4.3.1
• 4.4.0
• 4.4.1
• 4.4.2
• 4.5.0
• 4.5.1
• 4.5.2

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion