CVE-2016-5789
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 · uneditedA Cross-site Request Forgery issue was discovered in JanTek JTC-200, all versions. An attacker could perform actions with the same permissions as a victim user, provided the victim has an active session and is induced to trigger the malicious request.
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 · high confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in JanTek JTC-200 web application. The application lacks proper anti-CSRF protections on state-changing operations, allowing attackers to trick authenticated users into unknowingly executing unauthorized actions. Since the attacker cannot read responses (same-origin policy), this is a one-click attack requiring social engineering.
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 dataall versionsCVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Identify if JanTek JTC-200 web application is runningAccess the web interface of the device/application (typically on port 80 or 443) and confirm you have reached a JanTek JTC-200 login page or authenticated interfaceAffected if The target system presents a JanTek JTC-200 web interface for authentication or administration
-
Check for anti-CSRF token presence in state-changing formsLog into the web application, navigate to any form that performs state-changing actions (such as configuration changes, user management, or device control), and inspect the HTML source to see if a unique anti-CSRF token or random value is included as a hidden fieldAffected if Forms used for state-changing operations do not contain anti-CSRF tokens or unique session-bound values
-
Inspect session cookie SameSite attributeUsing browser developer tools or a command-line tool like curl, examine the session cookies set by the application and check for the SameSite attributeAffected if Session cookies lack the SameSite attribute or are set to 'None' without Secure flag
-
Verify Origin or Referer header validationSubmit a state-changing request from an external origin (different domain or IP) and observe whether the application rejects the request due to missing or invalid Origin/Referer headersAffected if The application accepts state-changing requests without validating the Origin or Referer header and processes them normally
-
Test for CSRF vulnerability with a crafted requestFrom a different origin (not the application server), create a state-changing request without anti-CSRF tokens and observe if the action is executed when an authenticated user visits the malicious pageAffected if State-changing operations succeed when initiated from a cross-origin request without proper anti-CSRF validation
If the JTC-200 web application is running and state-changing forms lack anti-CSRF tokens, session cookies lack SameSite attributes, and the application does not validate Origin/Referer headers, the environment is vulnerable to CVE-2016-5789.
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 dataImplement anti-CSRF tokens on all state-changing operations (forms, API endpoints) and validate the Origin or Referer header. Alternatively, set SameSite attribute on session cookies to 'Strict' or 'Lax'.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5789 — 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-2016-5789 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