dbcve.org
SalesiqWordPress extension · Zoho

CVE-2019-5963

HIGH · 8.8 CVSS v3.1 Published 2019-07-05
Fix available
A fix is available. Upgrade to after 1.0.8 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross-site request forgery (CSRF) vulnerability in Zoho SalesIQ 1.0.8 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors.

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 confidence

Cross-site request forgery (CSRF) vulnerability in Zoho SalesIQ version 1.0.8 and earlier allows remote attackers to hijack the authentication of administrators by tricking them into submitting malicious requests while authenticated. The lack of proper CSRF tokens or origin validation allows attackers to perform unauthorized administrative actions on behalf of logged-in administrators.

MitigationImplement anti-CSRF tokens on all state-changing operations (forms, API endpoints) and validate the Origin/Referer headers server-side. Additionally, configure SameSite cookies for session management to provide defense-in-depth against CSRF attacks.

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
SalesiqWordPress extension
Affected:<= 1.0.8

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Zoho SalesIQ version
    Locate the installed Zoho SalesIQ version number through the product's admin interface, about page, or version lookup mechanism provided by the software
    Affected if the installed version is 1.0.8 or any earlier version (1.0.x where x is 8 or lower)
  2. Verify CSRF token implementation on forms
    Inspect the HTML source of state-changing forms (such as admin configuration, user management, or settings pages) to determine if a unique CSRF token is present as a hidden field for each form submission
    Affected if state-changing forms lack CSRF token hidden fields or use predictable/static token values
  3. Verify CSRF token implementation on API endpoints
    Examine API requests that perform state-changing operations (POST, PUT, DELETE methods) to confirm each request includes a valid, unique CSRF token in the request headers or body
    Affected if API endpoints for administrative actions accept requests without CSRF token validation
  4. Check Origin or Referer header validation
    Capture a legitimate administrative request using a web proxy and replay it with a modified or missing Origin/Referer header to see if the server accepts or rejects the request
    Affected if the server processes requests with mismatched or missing Origin/Referer headers without rejection
  5. Inspect session cookie configuration
    Examine the session cookie attributes (SameSite, Secure flags) set by Zoho SalesIQ using browser developer tools or by inspecting HTTP response headers
    Affected if session cookies lack the SameSite attribute or are set to 'None' without the Secure flag

A defender is affected if their Zoho SalesIQ installation is version 1.0.8 or earlier AND the application lacks CSRF tokens on state-changing operations AND does not validate Origin/Referer headers on administrative requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.0.8
Interim mitigation

Implement anti-CSRF tokens on all state-changing operations (forms, API endpoints) and validate the Origin/Referer headers server-side. Additionally, configure SameSite cookies for session management to provide defense-in-depth against CSRF attacks.

Fix this in Salesiq Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5963 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-5963 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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