dbcve.org
Webex Meetings OnlineApplication · Cisco

CVE-2019-15987

MEDIUM · 5.3 CVSS v3.1 Published 2019-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 web interface of the Cisco Webex Event Center, Cisco Webex Meeting Center, Cisco Webex Support Center, and Cisco Webex Training Center could allow an unauthenticated, remote attacker to guess account usernames. The vulnerability is due to missing CAPTCHA protection in certain URLs. An attacker could exploit this vulnerability by sending a crafted request to the web interface. A successful exploit could allow the attacker to know if a given username is valid and find the real name of the 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 confidence

This is an information disclosure vulnerability in Cisco Webex web interfaces where missing CAPTCHA protection on certain URLs allows unauthenticated attackers to enumerate valid usernames and retrieve associated real names by sending crafted requests to the application.

MitigationImplement CAPTCHA protection on the vulnerable authentication-related URLs to prevent automated username enumeration 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
Webex Meetings OnlineApplication
Affected:= 11.0.0
Webex Meetings ServerApplication
Affected:= 4.0
Webex Event CenterApplication
Affected:all versions
Webex Meeting CenterApplication
Affected:all versions
Webex Support CenterApplication
Affected:all versions
Webex Training CenterApplication
Affected:all versions

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 the Cisco Webex product and version in use
    Access the administration console or check the web interface footer/version page for the exact product name and version number (e.g., Cisco Webex Meetings Online 11.0.0, Cisco Webex Meetings Server 4.0, or one of the Webex component products)
    Affected if The installed product is Cisco Webex Meetings Online version 11.0.0, Cisco Webex Meetings Server version 4.0, or any version of Cisco Webex Event Center, Meeting Center, Support Center, or Training Center
  2. Locate authentication-related URLs in the Webex web interface
    Identify URLs related to user authentication, password reset, or account recovery functions (common paths include /pwdreset, /forgotpassword, or similar endpoints that handle user account lookups)
    Affected if These authentication-related URLs exist in the Webex deployment and are accessible without authentication
  3. Verify CAPTCHA protection on vulnerable endpoints
    Inspect the identified authentication URLs in a web browser or using a tool like curl to confirm whether a CAPTCHA challenge (such as reCAPTCHA, form-based CAPTCHA, or similar) is presented before or during username lookup operations
    Affected if No CAPTCHA challenge is present on the authentication-related URLs, allowing automated username enumeration without rate limiting or human verification
  4. Test for username enumeration vulnerability
    Send crafted HTTP requests to the authentication endpoints with different potential usernames (e.g., using Burp Intruder or similar tool) and observe whether the responses differentiate between valid and invalid usernames (valid usernames may return the associated real name or a different response code)
    Affected if The application returns different responses for valid versus invalid usernames, revealing real names without any CAPTCHA or rate limiting protection

A user is affected if they are running any of the listed Cisco Webex products and the authentication-related URLs lack CAPTCHA protection, allowing unauthenticated username enumeration.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement CAPTCHA protection on the vulnerable authentication-related URLs to prevent automated username enumeration attacks.

Fix this in Webex Meetings Online 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 help mitigating

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-15987 — 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-15987 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