# CVE-2019-1881: Cisco Industrial Network Director Cross-Site Request Forgery Vulnerability

> Unauthenticated attackers can trick users into performing arbitrary actions on Cisco Industrial Network Director via CSRF.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Jun 2019
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-qqwx-xvq5-wgvm

## What is CVE-2019-1881?

CVE-2019-1881 is a medium-severity vulnerability in Cisco Industrial Network Director, published on 5 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the web-based management interface of Cisco Industrial Network Director (IND) could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack and perform arbitrary actions on an affected device. The vulnerability is due to insufficient CSRF protections for the web-based management interface of the affected device. An attacker could exploit this vulnerability by persuading a user of the interface to follow a malicious link. A successful exploit could allow the attacker to use a web browser and the privileges of the user to perform arbitrary actions on an affected device. For more information about CSRF attacks and potential mitigations, see Understanding Cross-Site Request Forgery Threat Vectors.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2019-1881?

It affects 1 product.


Products: Cisco Industrial Network Director.

## How do I fix CVE-2019-1881?

No fix has been published for CVE-2019-1881 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-1881 being exploited?

There is no known exploitation of CVE-2019-1881 in the wild and no public exploit code.

Public exploit code:

- Proof of concept for Strapi CVE-2019-18818 - Unauthenticated Password Reset Vulnerability / Privilege Escalation (github_poc): https://github.com/Shadawks/Strapi-CVE-2019-1881

## Other vulnerabilities in Cisco Industrial Network Director

- [CVE-2023-20036](https://insights.sbomify.com/CVE-2023-20036/): Cisco Industrial Network Director Command Injection Vulnerability (critical 9.9)
- [CVE-2023-20038](https://insights.sbomify.com/CVE-2023-20038/): Hardcoded credentials in Cisco Industrial Network Director (high 8.8)
- [CVE-2019-1976](https://insights.sbomify.com/CVE-2019-1976/): Cisco Industrial Network Director Configuration Data Information Disclosure Vulnerability (high 7.5)
- [CVE-2019-1861](https://insights.sbomify.com/CVE-2019-1861/): Cisco Industrial Network Director Remote Code Execution Vulnerability (high 7.2)
- [CVE-2020-3567](https://insights.sbomify.com/CVE-2020-3567/): Cisco Industrial Network Director Denial of Service Vulnerability (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1881 and fix it if it is affected.

What it is: CVE-2019-1881 is a medium-severity vulnerability in Cisco Industrial Network Director, published on 5 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-1881 in the wild and no public exploit code.

Affected product: Cisco Industrial Network Director. 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-1881/ (Markdown: https://insights.sbomify.com/CVE-2019-1881/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1881
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1881
- OSV: https://osv.dev/vulnerability/CVE-2019-1881

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-1881/
Summaries are generated and may contain mistakes; the official description above is the record.