CVE-2005-3938 json
SQL injection vulnerability in Softbiz FAQ Script 1.1 and earler allows remote attackers to execute arbitrary SQL commands via the id param…
published 2005-12-01 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-3933
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.8%
- EPSS 3.8% chance of exploitation in 30 days, percentile 90%
- public exploits
- 5
- Exploit-DB
Summary
SQL injection vulnerability in Softbiz FAQ Script 1.1 and earler allows remote attackers to execute arbitrary SQL commands via the id parameter in (1) index.php, (2) faq_qanda.php, (3) refer_friend.php, (4) print_article.php, or (5) add_comment.php.
Timeline
- First public exploit (EDB-26677)
- Published
Exploit prediction
3.82% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-26677 SoftBiz FAQ 1.1 - 'add_comment.php?id' SQL Injection webapps, 2005-11-30
- EDB-26676 SoftBiz FAQ 1.1 - 'print_article.php?id' SQL Injection webapps, 2005-11-30
- EDB-26675 SoftBiz FAQ 1.1 - 'refer_friend.php?id' SQL Injection webapps, 2005-11-30
- EDB-26674 SoftBiz FAQ 1.1 - 'faq_qanda.php?id' SQL Injection webapps, 2005-11-30
- EDB-26673 SoftBiz FAQ 1.1 - 'index.php?cid' SQL Injection webapps, 2005-11-30
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/15653
vdb-entry, broken-link
-
secunia.com
/advisories/17809
third-party-advisory
-
pridels0.blogspot.com
/2005/11/softbiz-faq-script-multiple-sql-vuln.html
broken-link
-
osvdb.org
/21261
vdb-entry, broken-link
-
osvdb.org
/21258
vdb-entry, broken-link
-
osvdb.org
/21260
vdb-entry, broken-link
-
osvdb.org
/21257
vdb-entry, broken-link
-
osvdb.org
/21259
vdb-entry, broken-link
Sources
- CVE List CVE-2005-3938
- NVD CVE-2005-3938
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.