Webex Meetings ServerApplication · Cisco

CVE-2014-3305

MEDIUM · 6.8 CVSS v2.0 Published 2014-07-26
Fix available
A fix is available. Upgrade to after 1.5 or later.
See remediation →
77/100
Remediation priority · High
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
Cross-site request forgery (CSRF) vulnerability in the web framework in Cisco WebEx Meetings Server 1.5(.1.131) and earlier allows remote attackers to hijack the authentication of unspecified victims via unknown vectors, aka Bug ID CSCuj81735.

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 · moderate confidence

Cross-site request forgery (CSRF) vulnerability in Cisco WebEx Meetings Server 1.5(.1.131) and earlier allows remote attackers to hijack the authentication of unspecified victims by tricking authenticated users into making unintended requests to the web application.

MitigationImplement anti-CSRF tokens on all state-changing operations, enable SameSite cookie attributes, and apply vendor-provided patches for Cisco WebEx Meetings Server.

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 ServerApplication
Affected:<= 1.5\(.1.131\)= 1.5= 1.5\(.1.6\)

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 installed Cisco WebEx Meetings Server version
    Access the administration interface or check system files to retrieve the current software version number
    Affected if The installed version is 1.5(.1.131) or earlier, including exactly version 1.5 or 1.5(.1.6)
  2. Confirm WebEx Meetings Server web interface is accessible
    Verify the Cisco WebEx Meetings Server web application is running and reachable on the network
    Affected if The web interface is exposed and accessible to users or attackers
  3. Determine if state-changing operations lack CSRF protection
    Inspect forms and requests for state-changing actions (such as user management, meeting configuration, or settings modifications) and verify whether anti-CSRF tokens or SameSite cookie attributes are present
    Affected if State-changing POST/PUT/DELETE requests do not include unique anti-CSRF tokens or the session cookies lack SameSite attributes

A user is affected if their Cisco WebEx Meetings Server version is 1.5(.1.131) or earlier and the web application lacks anti-CSRF tokens on state-changing operations.

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 a release after 1.5
Interim mitigation

Implement anti-CSRF tokens on all state-changing operations, enable SameSite cookie attributes, and apply vendor-provided patches for Cisco WebEx Meetings Server.

Fix this in Webex Meetings Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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