MyBB 1.2.5 calendar.php month sql injection

Summaryinfo

A vulnerability classified as critical was found in MyBB 1.2.5. The affected element is an unknown function of the file calendar.php. The manipulation of the argument month results in sql injection. This vulnerability is reported as CVE-2007-2212. The attack can be launched remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability, which was classified as critical, was found in MyBB 1.2.5 (Content Management System). Affected is an unknown function of the file calendar.php. The manipulation of the argument month with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

Multiple SQL injection vulnerabilities in calendar.php in MyBB (aka MyBulletinBoard) 1.2.5 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) year or (2) month parameter. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

The weakness was disclosed 04/24/2007 (Website). The advisory is shared for download at xforce.iss.net. This vulnerability is traded as CVE-2007-2212 since 04/24/2007. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details and a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.

A public exploit has been developed in Perl. The exploit is shared for download at securityfocus.com. It is declared as highly functional. As 0-day the estimated underground price was around $5k-$25k. By approaching the search of inurl:calendar.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 (33814), Exploit-DB (3780), SecurityFocus (BID 23612†) and Secunia (SA24967†). The entry VDB-36371 is pretty similar. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Content Management System

Name

• MyBB

Version

• 1.2.5

License

• open-source

Website

• Product: https://mybb.com/

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion