CVE-2010-3481 json
Multiple SQL injection vulnerabilities in login.php in ApPHP PHP MicroCMS 1.0.1, when magic_quotes_gpc is disabled, allow remote attackers…
published 16y ago modified 4mo ago also EUVD-2010-3479
- cvss
- 6.8
- 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 login.php in ApPHP PHP MicroCMS 1.0.1, when magic_quotes_gpc is disabled, allow remote attackers to execute arbitrary SQL commands via the (1) user_name and (2) password variables, possibly related to include/classes/Login.php. NOTE: some of these details are obtained from third party information. NOTE: the password vector might not be vulnerable.
Is CVE-2010-3481 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-15011)
- Published
Exploit prediction
1.12% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15011 PHP microcms 1.0.1 - Multiple Vulnerabilities webapps, 2010-09-15
- securityfocus.com http://www.securityfocus.com/bid/43232 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 |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
exploit-db.com
/exploits/15011
exploit
-
securityfocus.com
/bid/43232
vdb-entry, exploit
-
secunia.com
/advisories/41492
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/41455
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/61810
vdb-entry
-
osvdb.org
/68073
vdb-entry
-
attrition.org
/pipermail/vim/2010-September/002439.html
mailing-list
Sources
- CVE List CVE-2010-3481
- NVD CVE-2010-3481
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.