Beaussier RoomPHPlanning 1.6 Login.php ID sql injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in Beaussier RoomPHPlanning 1.6. This issue affects some unknown processing of the file Login.php. The manipulation of the argument ID leads to sql injection. This vulnerability is uniquely identified as CVE-2009-4669. The attack is possible to be carried out remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Beaussier RoomPHPlanning 1.6. This issue affects an unknown functionality of the file Login.php. The manipulation of the argument id with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Multiple SQL injection vulnerabilities in RoomPHPlanning 1.6 allow remote attackers to execute arbitrary SQL commands via (1) the loginus parameter to Login.php or (2) the Old Password field to changepwd.php, and allow (3) remote authenticated administrators to execute arbitrary SQL commands via the id parameter to admin/userform.php.

The weakness was disclosed 03/05/2010 (Website). It is possible to read the advisory at milw0rm.com. The identification of this vulnerability is CVE-2009-4669 since 03/05/2010. 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. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:Login.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 Exploit-DB (8797) and Secunia (SA35237†). The entries VDB-52069 and VDB-52068 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Beaussier

Name

• RoomPHPlanning

Version

• 1.6

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