The js-support-ticket plugin before 2.0.6 for WordPress has CSRF.

published 2019-08-27 7y ago modified 2026-06-17 4mo ago also EUVD-2018-13526

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

Patch / fix

fixed in 1

joomsky js_help_desk 2.0.6

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

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

CVSS scores

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

Classification

Weakness

CWE-352 Cross-Site Request Forgery

Technology feeds

WordPress rss critical rss

References

wordpress.org /plugins/js-support-ticket/#developers
release-notes, third-party-advisory

Sources

CVE List CVE-2018-21002
NVD CVE-2018-21002

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.