dbcve.org
Unified MeetingplaceApplication · Cisco

CVE-2013-5494

MEDIUM · 6.8 CVSS v2.0 Published 2013-09-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Unified MeetingPlace Solution, as used in Unified MeetingPlace Web Conferencing and Unified MeetingPlace, allows remote attackers to hijack the authentication of arbitrary users, aka Bug IDs CSCui45209 and CSCui44674.

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 request forgery (CSRF) vulnerability in the web framework of Cisco Unified MeetingPlace allows remote attackers to hijack the authentication of arbitrary users by tricking authenticated users into visiting malicious pages that perform unauthorized actions on the vulnerable application.

MitigationImplement anti-CSRF tokens on all state-changing operations, validate Origin/Referer headers server-side, and configure SameSite cookie attributes to prevent cross-site requests.

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
Unified MeetingplaceApplication
Affected:all versions
Unified Meetingplace Web ConferencingApplication
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
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 if Cisco Unified MeetingPlace is installed
    Search for MeetingPlace installation directories or running services on the system. Check for processes named 'meetingplace' or 'mp' in running processes, or look for installation folders typically under /opt/cisco/meetingplace or C:\Program Files\Cisco\MeetingPlace
    Affected if The product is found installed or running on the system
  2. Confirm the web interface is accessible
    Attempt to access the web conferencing portal via browser or curl to common endpoints such as https://hostname/meetingplace or port 8443. Check if the login page or web console responds
    Affected if The web interface responds and accepts authentication requests
  3. Test for CSRF token presence in forms
    Log into the web interface and inspect the HTML source of state-changing forms (such as scheduling a meeting, modifying user settings, or admin functions). Look for hidden input fields containing tokens, or check if forms include unique identifiers in POST requests
    Affected if Forms lack CSRF token hidden fields and submissions succeed without requiring anti-CSRF tokens
  4. Verify Origin/Referer header validation
    Send a crafted POST request to a state-changing endpoint with an incorrect or missing Origin/Referer header (using curl or Burp). Observe if the request is accepted or rejected
    Affected if Requests without valid Origin/Referer headers are processed successfully, indicating no server-side validation
  5. Check SameSite cookie configuration
    Log into the web interface and inspect Set-Cookie headers in HTTP responses. Verify if SameSite attribute is set to 'Strict' or 'Lax', or is absent
    Affected if SameSite attribute is missing or set to 'None' on session cookies, allowing cross-site cookie transmission

If Cisco Unified MeetingPlace web interface is accessible and lacks anti-CSRF tokens, Origin/Referer validation, or proper SameSite cookie settings, the environment is vulnerable to CVE-2013-5494

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 anti-CSRF tokens on all state-changing operations, validate Origin/Referer headers server-side, and configure SameSite cookie attributes to prevent cross-site requests.

Fix this in Unified Meetingplace Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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