WoltLab Burning Board Lite 1.0.2 search.php sql injection

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.

A vulnerability was found in WoltLab Burning Board Lite 1.0.2 (Content Management System) and classified as critical. Affected by this issue is an unknown code of the file search.php. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. Impacted is confidentiality, integrity, and availability. An attacker might be able inject and/or alter existing SQL statements which would influence the database exchange. CVE summarizes:

Multiple SQL injection vulnerabilities in search.php in WoltLab Burning Board (wBB) Lite 1.0.2 pl3e allow remote attackers to execute arbitrary SQL commands via the (1) showposts, (2) sortby, and (3) sortorder parameters.

The weakness was released 12/20/2007 (Website). The advisory is available at vupen.com. This vulnerability is handled as CVE-2007-6518 since 12/24/2007. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known.

It is declared as proof-of-concept. The exploit is available at securityfocus.com.

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 SecurityFocus (BID 26973) and Secunia (SA28188).





CPE 2.3infoedit

CPE 2.2infoedit


VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.9

VulDB Base Score: 7.3
VulDB Temp Score: 6.9
VulDB Vector: 🔍
VulDB Reliability: 🔍



VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍


Class: Sql injection
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍


Threat Intelligenceinfoedit

Threat: 🔍
Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Remediation: 🔍


Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍


12/20/2007 🔍
12/20/2007 +0 days 🔍
12/21/2007 +0 days 🔍
12/21/2007 +0 days 🔍
12/24/2007 +2 days 🔍
12/24/2007 +0 days 🔍
03/16/2015 +2639 days 🔍
09/02/2017 +901 days 🔍


Vendor: https://www.woltlab.com/

Advisory: vupen.com
Status: Not defined

CVE: CVE-2007-6518 (🔍)
SecurityFocus: 26973 - Woltlab Burning Board Lite Search.PHP Multiple SQL Injection Vulnerabilities
Secunia: 28188 - Woltlab Burning Board Lite Multiple Vulnerabilities, Moderately Critical
OSVDB: 39497 - WoltLab Burning Board Lite search.php Multiple Parameter SQL Injection
Vupen: ADV-2007-4300

scip Labs: https://www.scip.ch/en/?labs.20161013


Created: 03/16/2015 01:43 PM
Updated: 09/02/2017 10:31 AM
Changes: (15) vulnerability_cvss2_nvd_av vulnerability_cvss2_nvd_ac vulnerability_cvss2_nvd_au vulnerability_cvss2_nvd_ci vulnerability_cvss2_nvd_ii vulnerability_cvss2_nvd_ai exploit_availability exploit_publicity exploit_url source_cve_assigned source_secunia source_secunia_date source_securityfocus_date source_securityfocus_class source_vupen
Complete: 🔍


No comments yet. Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!