CVE-2010-0610 json
Multiple SQL injection vulnerabilities in the Photoblog (com_photoblog) component for Joomla!
published 16y ago modified 4mo ago also EUVD-2010-0641
- 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 61%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in the Photoblog (com_photoblog) component for Joomla! allow remote attackers to execute arbitrary SQL commands via the blog parameter in an images action to index.php. NOTE: a separate vector for the id parameter to detail.php may also exist.
Is CVE-2010-0610 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-11337)
- Published
Exploit prediction
0.97% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-11337 Joomla! Component com_photoblog - Blind SQL Injection webapps, 2010-02-06
- securityfocus.com http://www.securityfocus.com/bid/38136 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1002-exploits/joomlaphotoblog-bsql.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/11337
exploit
-
securityfocus.com
/bid/38136
vdb-entry, exploit
-
packetstormsecurity.org
/1002-exploits/joomlaphotoblog-bsql.txt
exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/56135
vdb-entry
Sources
- CVE List CVE-2010-0610
- NVD CVE-2010-0610
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.