Webex Business SuiteApplication · Cisco
CVE-2019-1926
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 · uneditedMultiple vulnerabilities in Cisco Webex Network Recording Player for Microsoft Windows and Cisco Webex Player for Microsoft Windows could allow an attacker to execute arbitrary code on an affected system. The vulnerabilities exist because the affected software improperly validates Advanced Recording Format (ARF) and Webex Recording Format (WRF) files. An attacker could exploit these vulnerabilities by sending a user a malicious ARF or WRF file through a link or email attachment and persuading the user to open the file with the affected software on the local system. A successful exploit could allow the attacker to execute arbitrary code on the affected system with the privileges of the targeted user.
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 confidenceThe vulnerability exists in Cisco Webex Network Recording Player and Cisco Webex Player for Microsoft Windows, where improper validation of Advanced Recording Format (ARF) and Webex Recording Format (WRF) files allows attackers to execute arbitrary code. Attackers deliver maliciously crafted ARF or WRF files via links or email attachments, and successful exploitation grants code execution with the privileges of the user who opens the file.
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
Webex Business SuiteApplication
< 39.5.5
Webex Meetings OnlineApplication
< 1.3.43
Webex Meetings ServerApplication
= 2.8= 3.0= 3.0mr2= 4.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Locate Webex Player installation directoryCheck common Windows installation paths for Cisco Webex players: %ProgramFiles%\Webex\Webex Player\ or %ProgramFiles(x86)%\Webex\Webex Player\. Also search for files named 'WebexPlayer.exe' or 'WebexNFLPlayer.exe' across the system using file search.Affected if Webex Player executable files are found on the system
-
Retrieve installed Webex Player versionRight-click the Webex Player executable file, select Properties, then view the Details tab to read the Product Version field. Alternatively, run 'wmic product get name,version' or check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Webex-related entries.Affected if Version information cannot be obtained or shows an unpatched version
-
Compare version against affected rangesMatch your installed version number to these vulnerable ranges: Cisco Webex Business Suite versions earlier than 39.5.5; Cisco Webex Meetings Online versions earlier than 1.3.43; Cisco Webex Meetings Server versions 2.8, 3.0, 3.0mr2, or 4.0Affected if Installed version falls within any of these ranges: < 39.5.5 for Webex Business Suite, < 1.3.43 for Webex Meetings Online, or exactly 2.8, 3.0, 3.0mr2, or 4.0 for Webex Meetings Server
-
Verify file type handling configurationCheck if the system has .arf and .wrf file extensions associated with Webex Player by examining Windows Default Programs settings or searching the registry for .arf and .wrf file associations under HKCR\.arf and HKCR\.wrfAffected if ARF or WRF file extensions are associated with Webex Player on the system
A user is affected if Webex Player is installed with a version matching the affected ranges AND the player is configured to handle ARF or WRF files, allowing code execution when a user opens a maliciously crafted recording file.
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 data1.3.4339.5.5
Apply the vendor-provided security patches from Cisco for affected Webex Player versions. Until patched, users should not open untrusted ARF or WRF files received via email or links.
Fix this in Webex Business Suite
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1926 — 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-2019-1926 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