CVE-2005-3748 json
SQL injection vulnerability in the Search module in Tru-Zone Nuke ET 3.2, and possibly earlier versions, allows remote attackers to execute…
published 2005-11-22 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-3743
- 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 68%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in the Search module in Tru-Zone Nuke ET 3.2, and possibly earlier versions, allows remote attackers to execute arbitrary SQL commands via the query parameter.
Patch / fix
Timeline
- First public exploit (EDB-26545)
- Published
Exploit prediction
1.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-26545 Tru-Zone Nuke ET 3.x - Search Module SQL Injection webapps, 2005-11-21
- lostmon.blogspot.com http://lostmon.blogspot.com/2005/11/nuke-et-search-module-query-variable.html referenced PoC, tagged "exploit" by a source, unverified
- osvdb.org http://www.osvdb.org/21002 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/15519 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 |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
secunia.com
/advisories/17638
third-party-advisory, patch, vendor-advisory
-
lostmon.blogspot.com
/2005/11/nuke-et-search-module-query-variable.html
exploit, patch, vendor-advisory
-
osvdb.org
/21002
vdb-entry, exploit
-
securityfocus.com
/bid/15519
vdb-entry, exploit
-
vupen.com
/english/advisories/2005/2516
vdb-entry, vendor-advisory
Sources
- CVE List CVE-2005-3748
- NVD CVE-2005-3748
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.