CVE-2007-0373 json
Multiple SQL injection vulnerabilities in Joomla!
published 2007-01-19 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-0375
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 12.3%
- EPSS 12.3% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
Multiple SQL injection vulnerabilities in Joomla! 1.5.0 Beta allow remote attackers to execute arbitrary SQL commands via (1) the searchword parameter in certain files; the where parameter in (2) plugins/search/content.php or (3) plugins/search/weblinks.php; the text parameter in (4) plugins/search/contacts.php, (5) plugins/search/categories.php, or (6) plugins/search/sections.php; or (7) the email parameter in database/table/user.php, which is not properly handled by the check function.
Exploit prediction
12.30% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- securityfocus.com http://www.securityfocus.com/bid/22122 referenced PoC, tagged "exploit" by a source, unverified
- archives.neohapsis.com http://archives.neohapsis.com/archives/fulldisclosure/2007-01/0355.html referenced PoC, tagged "exploit" by a source, unverified
- hackers.ir http://www.hackers.ir/advisories/festival.txt 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 |
References
-
securityfocus.com
/bid/22122
vdb-entry, exploit, vendor-advisory
-
archives.neohapsis.com
/archives/fulldisclosure/2007-01/0355.html
mailing-list, exploit
-
hackers.ir
/advisories/festival.txt
exploit
-
osvdb.org
/32528
vdb-entry
-
osvdb.org
/32527
vdb-entry
-
securityfocus.com
/archive/1/459203/100/0/threaded
mailing-list
-
osvdb.org
/32531
vdb-entry
-
osvdb.org
/32529
vdb-entry
-
osvdb.org
/32533
vdb-entry
-
osvdb.org
/32530
vdb-entry
-
osvdb.org
/32532
vdb-entry
Sources
- CVE List CVE-2007-0373
- NVD CVE-2007-0373
Fencer Vulns 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.