Unified MeetingplaceApplication · Cisco
CVE-2015-0702
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 · uneditedUnrestricted file upload vulnerability in the Custom Prompts upload implementation in Cisco Unified MeetingPlace 8.6(1.9) allows remote authenticated users to execute arbitrary code by using the languageShortName parameter to upload a file that provides shell access, aka Bug ID CSCus95712.
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 confidenceUnrestricted file upload vulnerability in the Custom Prompts upload feature of Cisco Unified MeetingPlace 8.6(1.9) allows remote authenticated users to upload arbitrary files via the languageShortName parameter, enabling them to deploy files that provide shell access and execute arbitrary code on the affected system.
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
= 8.6\(1.9\)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
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:S/C:C/I:C/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco Unified MeetingPlace versionCheck the installed version of Cisco Unified MeetingPlace by accessing the system via CLI or administrative web interface. Look in system information or about pages for the exact version string.Affected if The installed version is exactly 8.6(1.9)
-
Verify Custom Prompts feature statusAccess the Cisco Unified MeetingPlace administrative interface and navigate to the Custom Prompts or Audio Setup section. Check if the upload functionality for custom prompts is present and accessible.Affected if The Custom Prompts upload feature is enabled and accessible in the web interface
-
Inspect web-accessible directories for unexpected filesExamine directories typically used for custom prompts uploads, such as /meetingplace/custom_prompts, /mp3, or similar web-accessible folders. Look for file types that are not standard audio files (e.g., .jsp, .php, .asp, .exe, .sh).Affected if Non-audio file types or executable scripts are found in custom prompts upload directories
-
Review web server logs for upload activityCheck web server access and error logs for POST requests to the custom prompts upload endpoint, particularly those containing suspicious file extensions or the languageShortName parameter with unusual values.Affected if Log entries show upload requests with unexpected file types or extensions via the Custom Prompts feature
-
Check for unauthorized shell access scriptsSearch web directories for files with extensions associated with shell access (.jsp, .php, .asp, .cgi, .pl, .sh) that were not explicitly uploaded by administrators.Affected if Shell scripts or web shells are found in web-accessible directories
A system is affected if it is running Cisco Unified MeetingPlace version 8.6(1.9) with the Custom Prompts upload feature enabled and accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedApply available Cisco patches for this vulnerability. If no patch exists, disable the Custom Prompts upload feature, implement strict file type validation and extension whitelisting on the server side, store uploaded files outside the webroot, and ensure proper authentication and authorization checks are enforced for all upload operations.
Upgrade to the fixed release specified in the Cisco security advisory for CVE-2015-0702 (Bug ID CSCus95712) - contact Cisco TAC for the exact fixed version/branch
- 1. Verify current version of Cisco Unified MeetingPlace by checking the About page in the admin interface or running 'show version' in CLI
- 2. Contact Cisco Technical Assistance Center (TAC) to obtain the specific security update for CSCus95712
- 3. Request and apply the relevant security patch or upgrade to a fixed release as specified in the Cisco security advisory
- 4. After applying the fix, verify the Custom Prompts upload functionality works correctly
- 5. Test that the languageShortName parameter is now properly validated and restricted to expected file types
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Unified Meetingplace
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2015-0702 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-0702 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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