Unity ConnectionApplication · Cisco
CVE-2016-1304
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 scripting (XSS) vulnerability in Cisco Unity Connection 10.5(2.3009) allows remote attackers to inject arbitrary web script or HTML via a crafted value, aka Bug ID CSCux82596.
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 confidenceCross-site scripting (XSS) vulnerability in Cisco Unity Connection version 10.5(2.3009) allows remote attackers to inject arbitrary web script or HTML via a crafted value submitted to the web interface, potentially allowing session hijacking or defacement.
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
Unity ConnectionApplication
= 10.5\(2.3009\)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
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 Unity Connection is installedCheck your system for Cisco Unity Connection software. On the server, look for the installation directory (typically under /opt or C:\Program Files\Cisco\Unity Connection) or check running services for Unity Connection processes.Affected if Cisco Unity Connection software is present on the system
-
Identify the installed Unity Connection versionAccess the Cisco Unity Connection administrative interface or CLI. From the CLI, use the 'show version' command or 'show inventory' command. From the web admin, navigate to About or System Settings to view the version information.Affected if The displayed version is exactly 10.5(2.3009)
-
Verify the web interface is enabledCheck if the Cisco Unity Connection web interface (HTTPS/HTTP ports 443/80) is accessible and running. Use netstat or a port scanner to confirm ports 443 or 80 are listening on the Unity Connection server.Affected if The web interface ports (443/HTTPS or 80/HTTP) are open and responding
-
Confirm web forms accept user inputLog into the Unity Connection web interface and navigate to any web-based form (such as search, user creation, or messaging forms). Test whether the form accepts input through the value parameter.Affected if Web forms are accessible and accept user-submitted values
You are affected if Cisco Unity Connection version 10.5(2.3009) is installed AND the web interface is enabled and accessible, as the XSS vulnerability resides in web form handling.
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 the Cisco patch for CVE-2016-1304 (Bug ID CSCux82596) which updates Cisco Unity Connection to a patched version. As an interim control, implement input validation on web forms or deploy a WAF rule to sanitize script injection attempts in the value parameter.
Fix this in Unity Connection
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1304 — 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-2016-1304 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