CVE-2005-3208 json
Multiple SQL injection vulnerabilities in (1) aeNovo, (2) aeNovoShop and (3) aeNovoWYSI allow remote attackers to execute arbitrary SQL cod…
published 2005-10-14 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-3207
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 2
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in (1) aeNovo, (2) aeNovoShop and (3) aeNovoWYSI allow remote attackers to execute arbitrary SQL code via (a) the password parameter in control.asp, and (b) the strSQL parameter in search.asp, which can enable XSS attacks in resulting error messages.
Timeline
- First public exploit (EDB-26334)
- Published
Exploit prediction
2.15% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-26334 Aenovo - '/incs/searchdisplay.asp?strSQL' SQL Injection webapps, 2005-10-07
- EDB-26333 Aenovo - '/Password/default.asp?Password' SQL Injection webapps, 2005-10-07
- kapda.ir http://www.kapda.ir/advisory-78.html referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/15038 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
References
-
kapda.ir
/advisory-78.html
exploit, vendor-advisory
-
securityfocus.com
/bid/15038
vdb-entry, exploit
-
secunia.com
/advisories/17117/
third-party-advisory, vendor-advisory
-
osvdb.org
/19936
vdb-entry
-
securityfocus.com
/bid/15036
vdb-entry
-
marc.info
/?l=bugtraq&m=112872593432359&w=2
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/22553
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/22551
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/22547
vdb-entry
-
osvdb.org
/19937
vdb-entry
Sources
- CVE List CVE-2005-3208
- NVD CVE-2005-3208
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.