Identity Services EngineApplication · Cisco
CVE-2019-1941
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 management interface of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web-based management interface of an affected device. The vulnerability exists because the web-based management interface does not properly validate user-supplied input. An attacker could exploit this vulnerability by persuading a user to click a malicious link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information. At the time of publication, this vulnerability affected Cisco ISE running software releases prior to 2.4.0 Patch 9 and 2.6.0.
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 confidenceCross-site scripting (XSS) vulnerability in Cisco Identity Services Engine web-based management interface due to improper validation of user-supplied input. An unauthenticated, remote attacker can inject malicious script code via a crafted link that executes in the context of the affected interface when a user clicks it.
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
Identity Services EngineApplication
< 2.4.0= 2.4\(0.902\)= 2.4.0= 2.5\(0.225\)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.
-
Check Cisco ISE version via CLILog into the Cisco ISE CLI and run the command: `show version`. Look for the software version number in the output.Affected if The version shown is < 2.4.0, equals 2.4(0.902), equals 2.4.0 without patch 9+, or equals 2.5(0.225)
-
Verify patch level on 2.4.0 installationsIf the version shows 2.4.0, check the patch bundle number by running `show version | include Patch` or checking Administration > System > Deployment in the web UI.Affected if Running 2.4.0 with patch number less than 9, or no patch installed
-
Confirm web-based management interface is accessibleAttempt to reach the ISE web interface at the admin URL (typically https://<ise-host>/admin/). Check if the login page loads.Affected if The web management interface is exposed and accessible (the vulnerability requires this vector to be exploitable)
-
Check current software version in web UILog into the web UI and navigate to Administration > System > Deployment, or check the About page under System > Settings. Note the exact version and patch string.Affected if Version displayed matches the affected versions: < 2.4.0, 2.4(0.902), 2.4.0 (pre-patch 9), or 2.5(0.225)
You are affected if Cisco ISE is running any version before 2.4.0, or specifically versions 2.4(0.902), 2.4.0 without patch 9+, or 2.5(0.225), and the web-based management interface is accessible.
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 data2.4.0
Upgrade Cisco ISE to version 2.4.0 Patch 9 or later, or version 2.6.0 or later. This is a software update remediation requiring a standard upgrade procedure.
Fix this in Identity Services Engine
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1941 — 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-1941 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