SQL Injection exists in the CheckList 1.1.1 component for Joomla!

published 2018-02-22 8y ago modified 2026-06-17 4mo ago also EUVD-2018-19050

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 8.7%; EPSS 8.7% chance of exploitation in 30 days, percentile 95%
public exploits: 1; Exploit-DB

SQL Injection exists in the CheckList 1.1.1 component for Joomla! via the title_search, tag_search, name_search, description_search, or filter_order parameter.

Is CVE-2018-7318 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 Fencer

Timeline

2018-02-22 First public exploit (EDB-44163)
2018-02-22 Published

Exploit prediction

8.65% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

EDB-44163 Joomla! Component CheckList 1.1.1 - SQL Injection webapps, 2018-02-22

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/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

exploit-db.com /exploits/44163
exploit, third-party-advisory, vdb-entry
oracle.com /security-alerts/cpujan2021.html
third-party-advisory

Sources

CVE List CVE-2018-7318
NVD CVE-2018-7318

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.