Industrial Network DirectorApplication · Cisco

CVE-2019-1882

MEDIUM · 5.4 CVSS v3.0 Published 2019-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
A vulnerability in Cisco Industrial Network Director could allow an authenticated, remote attacker to conduct stored cross-site scripting (XSS) attacks. The vulnerability is due to improper validation of content submitted to the affected application. An attacker could exploit this vulnerability by sending requests containing malicious values to the affected system. A successful exploit could allow the attacker to conduct XSS attacks.

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 confidence

Stored XSS vulnerability in Cisco Industrial Network Director where improper validation of user-submitted content allows authenticated attackers to inject malicious JavaScript that executes when other users view the affected content.

MitigationApply Cisco's vendor patch when available. Until then, limit administrative access to the application and monitor for suspicious user submissions.

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
Industrial Network DirectorApplication
Affected:= 1.5\(0.250\)

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Cisco Industrial Network Director is installed
    Locate the installation directory or check running services for 'Cisco Industrial Network Director' or 'IND' processes. Typically installed under /opt/cisco/ind/ or C:\Program Files\Cisco\IND\ on Windows.
    Affected if The product is not installed or not present on the system
  2. Identify the installed version
    Access the product web interface and navigate to Administration > System > Software Updates, or check the version file in the installation directory (typically version.txt or about page in the GUI).
    Affected if The version is exactly 1.5(0.250)
  3. Determine if user-submitted content features are enabled
    Check if the application has features that accept user-generated content such as device naming, custom labels, topology annotations, or user profile fields. Review the Administration > User Management and Topology > Custom Views sections.
    Affected if User input fields or content submission features are accessible to authenticated users
  4. Verify authenticated user access exists
    Review user accounts in Administration > User Management. Check if there are non-admin users or if the authentication mechanism allows user login.
    Affected if Authenticated users (including low-privilege users) can access the application

The environment is affected if Cisco Industrial Network Director version 1.5(0.250) is running AND authenticated users can access user-submitted content features where malicious JavaScript could be stored and executed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco's vendor patch when available. Until then, limit administrative access to the application and monitor for suspicious user submissions.

Fix this in Industrial Network Director Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1882 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1882 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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