CVE-2017-8917 in the critical feed json
SQL injection vulnerability in Joomla!
published 2017-05-17 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-17857
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 99.8%
- EPSS 99.8% chance of exploitation in 30 days, percentile 99.9%
- public exploits
- 3
- Metasploit, Exploit-DB, plus a Nuclei check
Summary
SQL injection vulnerability in Joomla! 3.7.x before 3.7.1 allows attackers to execute arbitrary SQL commands via unspecified vectors.
Patch / fix
Timeline
- First public exploit (Metasploit exploit/unix/webapp/joomla_comfields_sqli_rce)
- Published
Exploit prediction
99.83% chance of exploitation in the next 30 days, higher than 99.9% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/unix/webapp/joomla_comfields_sqli_rce Joomla Component Fields SQLi Remote Code Execution metasploit exploit, excellent rank, 2017-05-17
- EDB-44358 Joomla! Component Fields - SQLi Remote Code Execution (Metasploit) webapps, 2018-03-29
- EDB-42033 Joomla! 3.7.0 - 'com_fields' SQL Injection webapps, 2017-05-19
- Nuclei template Joomla! <3.7.1 - SQL Injection nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| 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
-
developer.joomla.org
/security-centre/692-20170501-core-sql-injection.html
patch, vendor-advisory
-
exploit-db.com
/exploits/44358/
exploit, third-party-advisory, vdb-entry
-
exploit-db.com
/exploits/42033/
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/98515
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1038522
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-8917
- NVD CVE-2017-8917
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.