CVE-2006-3543 json
Multiple SQL injection vulnerabilities in Invision Power Board (IPB) 1.x and 2.x allow remote attackers to execute arbitrary SQL commands v…
published 2006-07-13 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-3538
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in Invision Power Board (IPB) 1.x and 2.x allow remote attackers to execute arbitrary SQL commands via the (1) idcat and (2) code parameters in a ketqua action in index.php; the id parameter in a (3) Attach and (4) ref action in index.php; the CODE parameter in a (5) Profile, (6) Login, and (7) Help action in index.php; and the (8) member_id parameter in coins_list.php. NOTE: the developer has disputed this issue, stating that the "CODE attribute is never present in an SQL query" and the "'ketqua' [action] and file 'coin_list.php' are not standard IPB 2.x features". It is unknown whether these vectors are associated with an independent module or modification of IPB
Timeline
- First public exploit (EDB-28167)
- Published
Exploit prediction
1.09% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-28167 Invision Power Board (IP.Board) 1.x/2.x - Multiple SQL Injections webapps, 2006-07-05
- securityfocus.com http://www.securityfocus.com/bid/18836 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
-
securityfocus.com
/bid/18836
vdb-entry, exploit
-
securityreason.com
/securityalert/1231
third-party-advisory
-
securityfocus.com
/archive/1/439145/100/0/threaded
mailing-list
-
osvdb.org
/30084
vdb-entry
-
securityfocus.com
/archive/1/439602/100/0/threaded
mailing-list
Sources
- CVE List CVE-2006-3543
- NVD CVE-2006-3543
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.