dbcve.org
Whatsapp DesktopApplication · Whatsapp

CVE-2019-11928

MEDIUM · 6.1 CVSS v3.1 Published 2020-09-03
Fix available
A fix is available. Upgrade to 0.3.4932 or later.
See remediation →
68/100
Remediation priority · Elevated
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 input validation issue in WhatsApp Desktop versions prior to v0.3.4932 could have allowed cross-site scripting upon clicking on a link from a specially crafted live location message.

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

A cross-site scripting vulnerability in WhatsApp Desktop versions prior to v0.3.4932 allows attackers to execute arbitrary JavaScript via malicious links embedded in specially crafted live location messages, exploiting insufficient input validation of message content.

MitigationUpdate WhatsApp Desktop to version v0.3.4932 or later to remediate this vulnerability.

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
Whatsapp DesktopApplication
Affected:< 0.3.4932

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Locate installed WhatsApp Desktop version
    Open WhatsApp Desktop, then go to Help > About WhatsApp Desktop (Windows) or WhatsApp > About WhatsApp (Mac). Alternatively, on Windows check Programs and Features or the Windows Registry for the installed version.
    Affected if Unable to determine or version not visible
  2. Compare version against vulnerable range
    Note the full version number displayed (e.g., 0.3.xxxx). Compare it numerically to 0.3.4932. All versions below 0.3.4932 are affected.
    Affected if Installed version is less than 0.3.4932 (e.g., 0.3.4910, 0.3.4800, etc.)
  3. Verify desktop client in use
    Confirm this is the standalone WhatsApp Desktop application, not the web browser version (web.whatsapp.com) or mobile app.
    Affected if Using WhatsApp Desktop version prior to 0.3.4932

If the installed WhatsApp Desktop version is below 0.3.4932, the environment is affected by this XSS vulnerability.

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 0.3.4932 or later
Fixed in 0.3.4932
Interim mitigation

Update WhatsApp Desktop to version v0.3.4932 or later to remediate this vulnerability.

Fix this in Whatsapp Desktop Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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