CVE-2009-4628 json
SQL injection vulnerability in the TemplatePlaza.com TPDugg (com_tpdugg) component 1.1 for Joomla!
published 16y ago modified 4mo ago also EUVD-2009-4593
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in the TemplatePlaza.com TPDugg (com_tpdugg) component 1.1 for Joomla! allows remote attackers to execute arbitrary SQL commands via the id parameter in a tags action to index.php.
Patch / fix
Is CVE-2009-4628 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-9602)
- Published
Exploit prediction
1.61% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-9602 Joomla! Component TPDugg 1.1 - Blind SQL Injection webapps, 2009-09-09
- evilc0de.blogspot.com http://evilc0de.blogspot.com/2009/09/tpdugg-joomla-component-11-blind-sql.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
-
templateplazza.com
/extensions-updates/tpdugg-component-update-v-1.1.1.html
patch
-
exploit-db.com
/exploits/9602
exploit
-
evilc0de.blogspot.com
/2009/09/tpdugg-joomla-component-11-blind-sql.html
exploit
-
vupen.com
/english/advisories/2009/2610
vdb-entry, vendor-advisory
-
secunia.com
/advisories/36656
third-party-advisory, vendor-advisory
-
osvdb.org
/57894
vdb-entry
-
securityfocus.com
/bid/36321
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/53108
vdb-entry
Sources
- CVE List CVE-2009-4628
- NVD CVE-2009-4628
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.