CVE-2010-5028 json
SQL injection vulnerability in the JExtensions JE Job (com_jejob) component 1.0 for Joomla!
published 15y ago modified 4mo ago also EUVD-2010-4992
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 9.2%
- EPSS 9.2% chance of exploitation in 30 days, percentile 95%
- public exploits
- 2
- Exploit-DB, plus a Nuclei check
Summary
SQL injection vulnerability in the JExtensions JE Job (com_jejob) component 1.0 for Joomla! allows remote attackers to execute arbitrary SQL commands via the catid parameter in an item action to index.php.
Is CVE-2010-5028 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-12601)
- Published
Exploit prediction
9.25% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-12782 Joomla! Component JE Job 1.0 - 'catid' SQL Injection webapps, 2010-05-28
- EDB-12601 Joomla! Component JE Job 1.0 - Local File Inclusion webapps, 2010-05-14
- Nuclei template Joomla! Component JE Job 1.0 - Local File Inclusion nuclei detection template
- securityfocus.com http://www.securityfocus.com/bid/40193 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/12782
exploit
-
securityfocus.com
/bid/40193
vdb-entry, exploit
-
vupen.com
/english/advisories/2010/1269
vdb-entry, vendor-advisory
-
secunia.com
/advisories/39837
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/58599
vdb-entry
-
osvdb.org
/64708
vdb-entry
Sources
- CVE List CVE-2010-5028
- NVD CVE-2010-5028
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.