The kama-clic-counter plugin 3.4.9 for WordPress has SQL injection via the admin.php order parameter.

published 2019-09-13 7y ago modified 2026-06-17 4mo ago also EUVD-2017-9727

cvss: 8.1; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.0%; EPSS 2.0% chance of exploitation in 30 days, percentile 81%
public exploits: 0; none known

Is CVE-2017-18614 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

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

Exploits and checks

seclists.org https://seclists.org/fulldisclosure/2017/Feb/67 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.1	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	9.3	AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness

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

Technology feeds

WordPress rss critical rss

References

seclists.org /fulldisclosure/2017/Feb/67
exploit, mailing-list, third-party-advisory
wordpress.org /plugins/kama-clic-counter/#developers
release-notes, vendor-advisory

Sources

CVE List CVE-2017-18614
NVD CVE-2017-18614

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.