Webex MeetingsApplication · Cisco

CVE-2019-15960

MEDIUM · 5.4 CVSS v3.1 Published 2019-11-26
Fix available
A fix is available. Upgrade to 39.7.0 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
A vulnerability in the Webex Network Recording Admin page of Cisco Webex Meetings could allow an authenticated, remote attacker to elevate privileges in the context of the affected page. To exploit this vulnerability, the attacker must be logged in as a low-level administrator. The vulnerability is due to insufficient access control validation. An attacker could exploit this vulnerability by submitting a crafted URL request to gain privileged access in the context of the affected page. A successful exploit could allow the attacker to elevate privileges in the Webex Recording Admin page, which could allow them to view or delete recordings that they would not normally be able to access.

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

Insufficient access control validation in the Webex Network Recording Admin page allows a low-level administrator to submit crafted URL requests and gain elevated privileges, enabling unauthorized access to view or delete recordings outside their assigned scope.

MitigationApply Cisco's security updates for Webex Meetings when released; monitor Cisco PSIRT advisories for patch availability and verify the fix after implementation.

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 MeetingsApplication
Affected:< 39.7.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Identify Cisco Webex Meetings installation
    Locate Webex Meetings server or application installation and confirm it is Cisco Webex Meetings. Check for Webex services, installation directories, or administrative interfaces.
    Affected if Cisco Webex Meetings is installed and running in the environment
  2. Determine installed version
    Access the Webex administrative interface or check system information to find the exact Webex Meetings version number.
    Affected if The installed version is below 39.7.0 (for example, 39.6.x, 39.5.x, or earlier)
  3. Verify Network Recording Admin page access
    Log into Webex as an administrator and navigate to the Network Recording Admin page or equivalent recording management interface. Attempt to access recording management functions.
    Affected if The Network Recording Admin page is accessible to administrators in the environment
  4. Check for low-privilege administrator accounts
    Review the Webex user management or administrator role assignments to identify accounts with limited or low-level administrative privileges.
    Affected if There are administrator accounts with reduced privileges (non-full-admin) who can access the recording management features

The environment is affected if Cisco Webex Meetings version is below 39.7.0 AND the Network Recording Admin page is accessible to low-privilege administrator accounts.

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

Apply Cisco's security updates for Webex Meetings when released; monitor Cisco PSIRT advisories for patch availability and verify the fix after implementation.

Fix this in Webex Meetings Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-15960 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