Bitweaver up to 2.0.0 highlight sql injection

Summaryinfo

A vulnerability was found in Bitweaver 1.1.1 Beta/1.2.1/1.3/1.3.1/2.0.0. It has been declared as critical. This impacts an unknown function. Executing a manipulation of the argument highlight can lead to sql injection. This vulnerability is registered as CVE-2007-6375. It is possible to launch the attack remotely. Furthermore, an exploit is available.

Detailsinfo

A vulnerability classified as critical was found in Bitweaver 1.1.1 Beta/1.2.1/1.3/1.3.1/2.0.0 (Content Management System). This vulnerability affects some unknown processing. The manipulation of the argument highlight with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Multiple SQL injection vulnerabilities in Bitweaver 2.0.0 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) sort_mode parameter to wiki/list_pages.php and the (2) highlight parameter to search/index.php. NOTE: the researcher also reported injection via JavaScript code in the Search box, but this is probably a forced SQL error or other separate primary issue.

The weakness was published 12/14/2007 (Website). The advisory is shared for download at securityfocus.com. This vulnerability was named CVE-2007-6375 since 12/14/2007. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.

It is possible to download the exploit at exploit-db.com. It is declared as highly functional.

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 (38943), Exploit-DB (30880) and SecurityFocus (BID 26801†). Similar entries are available at VDB-40095 and VDB-40059. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Content Management System

Name

• Bitweaver

Version

• 1.1.1 Beta
• 1.2.1
• 1.3
• 1.3.1
• 2.0.0

License

• open-source

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