CVE-2010-4006 json
Multiple SQL injection vulnerabilities in search.php in WSN Links 5.0.x before 5.0.81, 5.1.x before 5.1.51, and 6.0.x before 6.0.1 allow re…
published 16y ago modified 4mo ago also EUVD-2010-3982
- 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 66%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in search.php in WSN Links 5.0.x before 5.0.81, 5.1.x before 5.1.51, and 6.0.x before 6.0.1 allow remote attackers to execute arbitrary SQL commands via the (1) namecondition or (2) namesearch parameter.
Is CVE-2010-4006 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-15607)
Exploit prediction
1.15% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15607 WSN Links - SQL Injection webapps, 2010-11-24
- uncompiled.com http://www.uncompiled.com/2010/10/wsn-links-sql-injection-vulnerability-cve-2010-4006/ referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/44593 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
-
exploit-db.com
/exploits/15607
exploit
-
uncompiled.com
/2010/10/wsn-links-sql-injection-vulnerability-cve-2010-4006/
exploit
-
securityfocus.com
/bid/44593
vdb-entry, exploit
-
archives.neohapsis.com
/archives/fulldisclosure/2010-10/0512.html
mailing-list
-
securityfocus.com
/archive/1/514585/100/0/threaded
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/62939
vdb-entry
Sources
- CVE List CVE-2010-4006
- NVD CVE-2010-4006
Fencer Intel 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.