CVE-2010-1708 json
Multiple SQL injection vulnerabilities in agentadmin.php in Free Realty allow remote attackers to execute arbitrary SQL commands via the (1…
published 16y ago modified 4mo ago also EUVD-2010-1728
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in agentadmin.php in Free Realty allow remote attackers to execute arbitrary SQL commands via the (1) login field (aka agentname parameter) or (2) password field (aka agentpassword parameter).
Is CVE-2010-1708 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-12411)
- Published
Exploit prediction
0.97% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-12411 FreeRealty(Free Real Estate Listing Software) - Authentication Bypass webapps, 2010-04-27
- securityfocus.com http://www.securityfocus.com/bid/39712 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1004-exploits/freerealty-sql.txt 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/12411
exploit
-
securityfocus.com
/bid/39712
vdb-entry, exploit
-
packetstormsecurity.org
/1004-exploits/freerealty-sql.txt
exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/58193
vdb-entry
Sources
- CVE List CVE-2010-1708
- NVD CVE-2010-1708
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.