Unified MeetingplaceApplication · Cisco
CVE-2015-0705
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 · uneditedCross-site request forgery (CSRF) vulnerability in the SOAP API endpoints of the web-services directory in Cisco Unified MeetingPlace 8.6(1.9) allows remote attackers to hijack the authentication of administrators for requests that create administrative accounts, aka Bug ID CSCus97494.
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 confidenceCSRF vulnerability in the SOAP API endpoints of Cisco Unified MeetingPlace 8.6(1.9) web-services directory allows remote attackers to hijack administrator authentication and create unauthorized administrative accounts by tricking authenticated admins into visiting malicious pages.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Cisco Unified MeetingPlace versionAccess the system administration interface or check the product version through the web portal. Navigate to Help > About or check the version displayed in the administration console. Alternatively, query the system via: show version or check the installed_packages on the underlying system.Affected if The installed version is exactly 8.6(1.9)
-
Identify exposed SOAP API endpointsCheck if the web-services directory is accessible. Navigate to the SOAP endpoint URLs typically found at /web-services/ or search for WSDL files (such as admin.wsdl) exposed by the application. Use a web scanner or manually browse to common SOAP paths.Affected if SOAP API endpoints are publicly accessible without authentication or with valid admin session
-
Verify CSRF protection on SOAP endpointsInspect HTTP responses from SOAP API endpoints for anti-CSRF tokens or SameSite cookie attributes. Submit a SOAP request without any CSRF token and observe if the request is processed or rejected.Affected if SOAP endpoints accept requests without requiring valid CSRF tokens or origin verification
-
Check for unauthorized administrative accountsLog into the administration console and review the list of administrative users in the user management section. Look for accounts that were not created by known administrators.Affected if There are administrative accounts that were not created by legitimate administrators
You are affected if you are running exactly version 8.6(1.9) and have accessible SOAP API endpoints that lack CSRF protection, allowing creation of unauthorized admin accounts.
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.
From vendor dataImplement anti-CSRF tokens and validation on all SOAP API endpoints, including SameSite cookie attributes and origin verification. Consider deploying a WAF with CSRF detection as an interim control.
Fix this in Unified Meetingplace
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing5.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0705 — 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-0705 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