CVE-2005-2989 json
Multiple SQL injection vulnerabilities in DeluxeBB 1.0 and 1.0.5 allow remote attackers to execute arbitrary SQL commands via the (1) tid p…
published 2005-09-19 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-2989
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 5
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in DeluxeBB 1.0 and 1.0.5 allow remote attackers to execute arbitrary SQL commands via the (1) tid parameter to topic.php, the uid parameter to (2) misc.php or (3) pm.php, or the fid parameter to (3) forums.php or (4) newpost.php.
Patch / fix
- secunia.com/advisories/16819 advisory
Timeline
- First public exploit (EDB-26268)
- Published
Exploit prediction
1.23% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-26268 DeluxeBB 1.0 - 'newpost.php' SQL Injection webapps, 2005-09-15
- EDB-26267 DeluxeBB 1.0 - 'pm.php' SQL Injection webapps, 2005-09-15
- EDB-26266 DeluxeBB 1.0 - 'forums.php' SQL Injection webapps, 2005-09-15
- EDB-26265 DeluxeBB 1.0 - 'misc.php' SQL Injection webapps, 2005-09-15
- EDB-26264 DeluxeBB 1.0 - 'topic.php' SQL Injection webapps, 2005-09-15
- secunia.com http://secunia.com/advisories/16819 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/14851 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
References
-
secunia.com
/advisories/16819
third-party-advisory, exploit, patch, vendor-advisory
-
securityfocus.com
/bid/14851
vdb-entry, exploit
-
vupen.com
/english/advisories/2005/1752
vdb-entry
Sources
- CVE List CVE-2005-2989
- NVD CVE-2005-2989
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.