dbcve.org
LivezillaApplication

CVE-2020-9758

CRITICAL · 9.6 CVSS v3.1 Published 2020-03-09
Fix available
A fix is available. Upgrade to 8.0.1.3 or later.
See remediation →
100/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
An issue was discovered in chat.php in LiveZilla Live Chat 8.0.1.3 (Helpdesk). A blind JavaScript injection lies in the name parameter. Triggering this can fetch the username and passwords of the helpdesk employees in the URI. This leads to a privilege escalation, from unauthenticated to user-level access, leading to full account takeover. The attack fetches multiple credentials because they are stored in the database (stored XSS). This affects the mobile/chat URI via the lgn and psswrd parameters.

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 confidence

LiveZilla Live Chat 8.0.1.3 contains a stored XSS vulnerability in the name parameter of chat.php. When an unauthenticated user submits a malicious JavaScript payload in the name field, it executes when helpdesk staff view the chat, exfiltrating stored credentials (usernames and passwords) via the lgn and psswrd parameters to an attacker-controlled URI, enabling full account takeover.

MitigationImplement strict input validation and output encoding on all user-supplied parameters (especially name, lgn, psswrd) in chat.php. Consider implementing Content Security Policy headers to mitigate JavaScript injection. Review and sanitize all data before storage and before rendering.

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
LivezillaApplication
Affected:< 8.0.1.3

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Check LiveZilla version
    Locate the version file or check the admin dashboard for the installed LiveZilla version. Common locations include a version.php file or the about/admin section.
    Affected if Installed version is lower than 8.0.1.3
  2. Verify chat.php is accessible
    Confirm that chat.php exists in the web root and is reachable via HTTP/HTTPS. This is the endpoint where unauthenticated users submit the name parameter.
    Affected if chat.php is exposed and accepts user input without authentication
  3. Inspect database for stored XSS in name field
    Query the chat/message database tables for the name field. Look for any stored scripts or unusual HTML/JavaScript content that may have been injected.
    Affected if Database contains unsanitized script tags or JavaScript in name-related fields
  4. Check for credential exfiltration patterns
    Review server logs and database for suspicious requests containing both lgn and psswrd parameters being sent to unusual or external URIs.
    Affected if Logs show attempts to exfiltrate credentials via lgn/psswrd parameters to unknown URIs
  5. Review chat.php input handling
    Examine the source code of chat.php to verify if the name parameter is being validated, sanitized, or encoded before storage and display.
    Affected if Name parameter is stored or displayed without proper sanitization or output encoding

A user is affected if LiveZilla version is below 8.0.1.3 and chat.php is accessible, allowing unauthenticated stored XSS that can capture credentials.

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.

dbcve · scoped
Upgrade available Upgrade to 8.0.1.3 or later
Fixed in 8.0.1.3
Interim mitigation

Implement strict input validation and output encoding on all user-supplied parameters (especially name, lgn, psswrd) in chat.php. Consider implementing Content Security Policy headers to mitigate JavaScript injection. Review and sanitize all data before storage and before rendering.

Recommended fix Moderate confidence

LiveZilla 8.0.1.3 or later

  1. Upgrade LiveZilla to version 8.0.1.3 or later to resolve the stored XSS vulnerability
  2. If upgrading is not immediately possible, implement Web Application Firewall (WAF) rules to filter malicious requests containing script tags in the name, lgn, and psswrd parameters
  3. Disable or restrict access to the mobile/chat endpoint if not required for business operations
  4. Implement strict input validation and output encoding for all user-supplied parameters, especially name, lgn, and psswrd
  5. Review and rotate any credentials that may have been exposed through this vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Livezilla Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-9758 — 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-2020-9758 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