MediasenseApplication · Cisco
CVE-2015-0736
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 Cisco MediaSense 10.5(1) and earlier allows remote attackers to hijack the authentication of arbitrary users, aka Bug ID CSCuu16728.
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 confidenceCSRF vulnerability in Cisco MediaSense 10.5(1) and earlier allows remote attackers to hijack authentication of arbitrary users by tricking authenticated users into submitting malicious requests. The application lacks proper anti-CSRF tokens or origin validation, enabling attackers to perform actions on behalf of victims without their knowledge.
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
MediasenseApplication
= 9.1\(1\)= 10.0\(1\)= 10.5\(1\)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 MediaSense installationLocate the Cisco MediaSense application on your system or check your inventory of installed software to verify MediaSense is deployedAffected if Cisco MediaSense is not installed on your environment - the check is not applicable
-
Identify the installed MediaSense versionAccess the MediaSense administration interface or check system inventory to determine the exact version number (such as 9.1(1), 10.0(1), or 10.5(1))Affected if The installed version matches 9.1(1), 10.0(1), 10.5(1), or any version earlier than 10.5(1)
-
Compare version against affected rangeCompare your identified version against the affected range: versions 9.1(1), 10.0(1), 10.5(1), and any earlier versionsAffected if Your version falls within or below 9.1(1) to 10.5(1)
-
Assess web interface accessibilityDetermine whether the MediaSense web management interface is accessible from network locations where untrusted sites could be browsedAffected if The web interface is exposed to users who might browse external sites while authenticated
You are affected if Cisco MediaSense version 9.1(1), 10.0(1), 10.5(1), or any earlier version is installed and its web interface is accessible to 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.
From vendor dataApply vendor-provided patch for CSCuu16728. As interim measure, users should avoid browsing other sites while logged into MediaSense and log out after each session.
Fix this in Mediasense
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2015-0736 — 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-0736 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