CVE-2019-1915
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 · uneditedA vulnerability in the web-based interface of Cisco Unified Communications Manager, Cisco Unified Communications Manager Session Management Edition (SME), Cisco Unified Communications Manager IM and Presence (Unified CM IM&P) Service, and Cisco Unity Connection could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack on an affected system. The vulnerability is due to insufficient CSRF protections by the affected software. An attacker could exploit this vulnerability by persuading a targeted user to click a malicious link. A successful exploit could allow the attacker to send arbitrary requests that could change the password of a targeted user. An attacker could then take unauthorized actions on behalf of the targeted user.
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 confidenceThis is a cross-site request forgery (CSRF) vulnerability in the web-based management interfaces of Cisco Unified Communications Manager, Unified CM IM&P Service, and Cisco Unity Connection. The affected software lacks proper CSRF protection mechanisms (such as anti-CSRF tokens), allowing unauthenticated attackers to craft malicious links that, when clicked by an authenticated administrator, can force the browser to send arbitrary requests that change user passwords or perform other unauthorized actions.
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= 10.5\(2.10000.5\)= 11.5\(1.10000.6\)= 12.0\(1.10000.10\)= 12.5\(1.10000.22\)= 11.5= 12.0= 12.5= 14.0= 12.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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Identify the Cisco UC productLog into the server CLI or check the installed applications to determine if the system is running Cisco Unified Communications Manager (CUCM), Cisco Unity Connection, or Unified CM IM&P Service. Common CLI command: 'show version active' or check the application inventory.Affected if The system runs any of the three affected products: CUCM, Unity Connection, or IM&P Service.
-
Determine the installed versionRun the CLI command 'show version' or access the Cisco Unified Communications Manager Administration page and navigate to 'Help > About' to retrieve the exact version number.Affected if The installed version matches or falls within these affected ranges: CUCM 10.5(2.10000.5), 11.5(1.10000.6), 12.0(1.10000.10), 12.5(1.10000.22); Unity Connection 11.5, 12.0, 12.5, 14.0; IM&P 12.5(1).
-
Verify web management interface is accessibleConfirm the Cisco web-based management interface is enabled and reachable. This is typically accessible on port 8443 or 443 (for example, https://<hostname>:8443/ccmadmin or https://<hostname>/cuadmin). Check if the web service is running via 'show web security' or similar CLI command.Affected if The web management interface is enabled and exposed, which is required for the CSRF vulnerability to be exploitable.
-
Check for CSRF protection tokensInspect the web forms in the management interface (such as user password change forms or admin configuration pages) by viewing the HTML source. Look for the presence of anti-CSRF tokens, hidden form fields, or unique request identifiers that validate the origin of requests. If these are missing, the system is likely vulnerable.Affected if The web forms lack anti-CSRF tokens or unique request validation mechanisms, indicating the vulnerability is present.
The system is affected if it runs any of the vulnerable product versions (CUCM 10.5.2 through 12.5.1, Unity Connection 11.5 through 14.0, or IM&P 12.5(1)) AND the web-based management interface is accessible without the protective anti-CSRF mechanisms in place.
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 vendor-supplied patch from Cisco Security Advisory. Until patched, warn users not to click untrusted links and consider implementing additional network-level access controls to the administrative interfaces.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1915 — 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-2019-1915 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