CVE-2018-21002
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe js-support-ticket plugin before 2.0.6 for WordPress has CSRF.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe js-support-ticket WordPress plugin before version 2.0.6 contains a Cross-Site Request Forgery (CSRF) vulnerability. Attackers can exploit this by tricking authenticated administrators into clicking malicious links or visiting crafted pages, causing the browser to send authenticated requests to the plugin's endpoints without the user's consent.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.0.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify js-support-ticket plugin is installedNavigate to WordPress admin > Plugins > Installed Plugins and look for 'Js Help Desk' or 'js-support-ticket' in the plugin listAffected if The plugin is not found in the installed plugins list
-
Check installed plugin versionClick on the plugin name to view its details, or inspect the plugin header in /wp-content/plugins/js-support-ticket/js-support-ticket.php to find the 'Version' fieldAffected if The version displayed is less than 2.0.6 (for example, 2.0.5, 2.0.4, etc.)
-
Confirm plugin is activeIn the Plugins list, verify that the plugin shows as 'Active' under the status columnAffected if The plugin is active and the version is below 2.0.6
-
Inspect plugin for anti-CSRF nonce implementation (optional deeper check)Examine the plugin's PHP files for state-changing actions (form submissions, admin actions) and check if they include wp_nonce_field() or check_admin_referer() callsAffected if The plugin code lacks nonce verification for sensitive operations and the version is below 2.0.6
The environment is affected if the Joomsky Js Help Desk (js-support-ticket) plugin is installed, active, and version is below 2.0.6, allowing CSRF attacks against authenticated administrators.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.0.6
Update the js-support-ticket plugin to version 2.0.6 or later, which should include proper anti-CSRF nonce verification for all state-changing operations.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-21002 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-21002 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data