# CVE-2019-1673: Cisco Identity Services Engine Cross-Site Scripting Vulnerability > An authenticated attacker can execute arbitrary script code or access sensitive browser-based information via a crafted link in the Cisco ISE web interface. - **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 8 Feb 2019 - **Updated:** 21 Nov 2024 - **Also known as:** GHSA-667v-j225-pqfx ## What is CVE-2019-1673? CVE-2019-1673 is a medium-severity cross-site scripting vulnerability in Cisco Identity Services Engine, published on 8 Feb 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description A vulnerability in the web-based management interface of Cisco Identity Services Engine (ISE) could allow an authenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web-based interface. The vulnerability is due to insufficient input validation of some parameters passed to the web-based management interface. An attacker could exploit this vulnerability by convincing a user of the interface to click a specific link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the interface or allow the attacker to access sensitive browser-based information. For information about fixed software releases, consult the Cisco bug ID at https://quickview.cloudapps.cisco.com/quickview/bug/CSCvn64652. When considering software upgrades, customers are advised to regularly consult the advisories for Cisco products, which are available from the Cisco Security Advisories and Alerts page, to determine exposure and a complete upgrade solution. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2019-1673? It affects 1 product. Products: Cisco Identity Services Engine. ## How do I fix CVE-2019-1673? No fix has been published for CVE-2019-1673 yet. Limit exposure of the affected software until one is available. ## Is CVE-2019-1673 being exploited? There is no known exploitation of CVE-2019-1673 in the wild and no public exploit code. ## Other vulnerabilities in Cisco Identity Services Engine - [CVE-2026-76460](https://insights.sbomify.com/CVE-2026-76460/): Cisco Identity Services Engine Incorrect Use of Privileged APIs (critical 10.0, exploited in the wild) - [CVE-2025-20337](https://insights.sbomify.com/CVE-2025-20337/): Cisco Identity Services Engine Injection (critical 10.0, exploited in the wild) - [CVE-2025-20281](https://insights.sbomify.com/CVE-2025-20281/): Cisco Identity Services Engine Injection (critical 10.0, exploited in the wild) - [CVE-2026-20130](https://insights.sbomify.com/CVE-2026-20130/): Cisco Identity Services Engine Hardening Release - Improper Neutralization Vulnerabilities (critical 10.0) - [CVE-2026-20192](https://insights.sbomify.com/CVE-2026-20192/): Cisco Identity Services Engine Hardening Release - Access Control Vulnerabilities (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-1673 and fix it if it is affected. What it is: CVE-2019-1673 is a medium-severity cross-site scripting vulnerability in Cisco Identity Services Engine, published on 8 Feb 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2019-1673 in the wild and no public exploit code. Affected product: Cisco Identity Services Engine. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-1673/ (Markdown: https://insights.sbomify.com/CVE-2019-1673/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1673 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1673 - OSV: https://osv.dev/vulnerability/CVE-2019-1673 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-1673/ Summaries are generated and may contain mistakes; the official description above is the record.