e107_admin/banlist.php in e107 2.1.8 allows SQL injection via the old_ip parameter.

published 2018-09-12 8y ago modified 2026-06-17 4mo ago also EUVD-2018-8233

cvss: 6.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits: 0; none known

Patch / fix

links 1

github.com/e107inc/e107@ec483e9 commit

Is CVE-2018-16389 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

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
NVD	3.0	6.5	CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
NVD	2.0	5.5	AV:N/AC:L/Au:S/C:P/I:P/A:N

Classification

Weakness

CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

github.com /e107inc/e107/commit/ec483e9379aa622bfcc1b853b189c74288771f27
patch, vendor-advisory
gist.github.com /ommadawn46/51e08e13e6980dcbcffb4322c29b93d0
third-party-advisory

Sources

CVE List CVE-2018-16389
NVD CVE-2018-16389

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.