CVE-2010-1522 json
Multiple SQL injection vulnerabilities in the BookLibrary Basic (com_booklibrary) component 1.5.3 before 1.5.3_2010_06_20 for Joomla!
published 16y ago modified 4mo ago also EUVD-2010-1549
- 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 71%
- public exploits
- 0
- none known
Summary
Multiple SQL injection vulnerabilities in the BookLibrary Basic (com_booklibrary) component 1.5.3 before 1.5.3_2010_06_20 for Joomla! allow remote attackers to execute arbitrary SQL commands via the bid[] parameter in a (1) lend_request or (2) save_lend_request action to index.php, the id parameter in a (3) mdownload or (4) downitsf action to index.php, or (5) the searchtext parameter in a search action to index.php.
Patch / fix
Is CVE-2010-1522 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 FencerExploit prediction
1.33% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).
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
-
ordasoft.com
/Download/Download-document/3-BookLibrary-1.5.3-Basic-for-Joomla-1.5.html
patch
-
ordasoft.com
/Download/View-document-details/3-BookLibrary-1.5.3-Basic-for-Joomla-1.5.html
patch
-
secunia.com
/advisories/40131
third-party-advisory, vendor-advisory
-
secunia.com
/secunia_research/2010-84/
vendor-advisory
-
securityfocus.com
/archive/1/512094/100/0/threaded
mailing-list
-
securityfocus.com
/bid/41264
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/59966
vdb-entry
-
osvdb.org
/65879
vdb-entry
Sources
- CVE List CVE-2010-1522
- NVD CVE-2010-1522
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.