CVE-2009-4650 json
SQL injection vulnerability in the Webee Comments (com_webeecomment) component 1.1.1, 1.2, and 2.0 for Joomla!
published 16y ago modified 4mo ago also EUVD-2009-4615
- 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
SQL injection vulnerability in the Webee Comments (com_webeecomment) component 1.1.1, 1.2, and 2.0 for Joomla! allows remote attackers to execute arbitrary SQL commands via the articleId parameter in a default action to index2.php. NOTE: some of these details are obtained from third party information.
Is CVE-2009-4650 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-33637)
- 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-33637 Joomla! Component Webee Comments 1.1/1.2 - 'index2.php' articleId SQL Injection webapps, 2009-11-15
- osvdb.org http://www.osvdb.org/62334 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/38204 referenced PoC, tagged "exploit" by a source, unverified
- jeffchannell.com http://jeffchannell.com/Joomla/webee-111-multiple-vulnerabilities.html 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
-
osvdb.org
/62334
vdb-entry, exploit
-
securityfocus.com
/bid/38204
vdb-entry, exploit
-
jeffchannell.com
/Joomla/webee-111-multiple-vulnerabilities.html
exploit
-
secunia.com
/advisories/38625
third-party-advisory, vendor-advisory
Sources
- CVE List CVE-2009-4650
- NVD CVE-2009-4650
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.