CVE-2006-3662 json
SQL injection vulnerability in index.php in ATutor 1.5.3 allows remote attackers to execute arbitrary SQL commands via the fid parameter.
published 2006-07-17 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-3657
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 69%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in index.php in ATutor 1.5.3 allows remote attackers to execute arbitrary SQL commands via the fid parameter. NOTE: this issue has been disputed by the vendor, who states "The mentioned SQL injection vulnerability is not possible." However, the relevant source code suggests that this issue may be legitimate, and the parameter is cleansed in 1.5.3.1
Timeline
- First public exploit (EDB-28192)
- Published
Exploit prediction
1.25% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-28192 ATutor 1.5.3 - Multiple Input Validation Vulnerabilities webapps, 2006-07-08
- archives.neohapsis.com http://archives.neohapsis.com/archives/bugtraq/2006-07/0096.html referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/18898 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
-
archives.neohapsis.com
/archives/bugtraq/2006-07/0096.html
mailing-list, exploit
-
securityfocus.com
/bid/18898
vdb-entry, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/27620
vdb-entry
-
osvdb.org
/28188
vdb-entry
-
securityfocus.com
/archive/1/440837/100/100/threaded
mailing-list
-
securityfocus.com
/archive/1/439873/100/100/threaded
mailing-list
Sources
- CVE List CVE-2006-3662
- NVD CVE-2006-3662
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.