Webex MeetingsApplication · Cisco

CVE-2018-0356

MEDIUM · 6.1 CVSS v3.0 Published 2018-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A vulnerability in the web framework of Cisco WebEx could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against the user of the web interface of an affected system. The vulnerability is due to insufficient input validation of certain parameters that are passed to the affected software via the HTTP GET and HTTP POST methods. An attacker who can convince a user to follow an attacker-supplied link could execute arbitrary script or HTML code in the user's browser in the context of an affected site. Cisco Bug IDs: CSCvi63757.

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

Cross-site scripting (XSS) vulnerability in Cisco WebEx web framework due to insufficient input validation of parameters passed via HTTP GET and POST methods. An unauthenticated remote attacker can inject malicious scripts through crafted links, executing arbitrary HTML or JavaScript in users' browsers within the context of the affected WebEx site.

MitigationApply the Cisco patch for bug CSCvi63757 to affected WebEx systems. Users should be warned to avoid clicking untrusted links until the patch is applied.

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:= t32

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.0/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. Identify if Cisco WebEx web interface is exposed
    Determine if your organization runs any Cisco WebEx web-facing services (typically at webex.com or custom WebEx sites). Check internal network scans or documentation for WebEx meeting server URLs.
    Affected if WebEx web interface is accessible and active
  2. Determine the Cisco WebEx Meetings version
    Log into the WebEx Administration site or check the server/host documentation for the installed WebEx Meetings version number.
    Affected if Version is Cisco Webex Meetings = t32 (exact version match)
  3. Check for unauthenticated HTTP parameter access
    Examine the WebEx login or meeting join page URLs. The vulnerability involves parameters passed via HTTP GET and POST methods that are not properly validated.
    Affected if The WebEx site accepts URL parameters or form inputs that are reflected in the page output without sanitization
  4. Verify input validation behavior
    Using a test account, submit a harmless test string (e.g., <script>alert('test')</script>) via URL parameters or form fields on the WebEx login/join page and observe if the string is executed or rendered as-is.
    Affected if The input is reflected back in the response without HTML encoding, allowing script execution

You are affected if you run Cisco WebEx Meetings version t32 and your WebEx web interface reflects unsanitized input in HTTP parameters.

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

Apply the Cisco patch for bug CSCvi63757 to affected WebEx systems. Users should be warned to avoid clicking untrusted links until the patch is applied.

Fix this in Webex Meetings Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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