CVE-2010-3484 json
SQL injection vulnerability in common.php in LightNEasy 3.2.1 allows remote attackers to execute arbitrary SQL commands via the handle para…
published 16y ago modified 4mo ago also EUVD-2010-3482
- 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 70%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in common.php in LightNEasy 3.2.1 allows remote attackers to execute arbitrary SQL commands via the handle parameter to LightNEasy.php, a different vector than CVE-2008-6593.
Patch / fix
- mapserver Debian 14, Debian 13, Debian 12 5.6.4-1
debian advisories DEBIAN-CVE-2010-3484
Is CVE-2010-3484 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
- First public exploit (EDB-15060)
- Published
Exploit prediction
1.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15060 LightNEasy CMS 3.2.1 - Blind SQL Injection webapps, 2010-09-20
- packetstormsecurity.org http://packetstormsecurity.org/1009-exploits/lightneasy-sql.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/43330 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/15060
exploit
-
packetstormsecurity.org
/1009-exploits/lightneasy-sql.txt
exploit
-
securityfocus.com
/bid/43330
vdb-entry, exploit
-
vupen.com
/english/advisories/2010/2457
vdb-entry, vendor-advisory
-
secunia.com
/advisories/41502
third-party-advisory, vendor-advisory
Sources
- CVE List CVE-2010-3484
- NVD CVE-2010-3484
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.