# CVE-2019-17118: Cross-site request forgery in n/a

> A CSRF vulnerability in WiKID 2FA Enterprise Server allows attackers to trick users into creating or deleting admin accounts and modifying user settings.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 17 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qrhm-956g-2f5j

## What is CVE-2019-17118?

CVE-2019-17118 is a high-severity vulnerability in n/a, published on 17 Oct 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 CSRF issue in WiKID 2FA Enterprise Server through 4.2.0-b2053 allows a remote attacker to trick an authenticated user into performing unintended actions such as (1) create or delete admin users; (2) create or delete groups; or (3) create, delete, enable, or disable normal users or devices.

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

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

It affects 1 product.


Products: Wikidsystems 2fa Enterprise Server.

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

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

## Is CVE-2019-17118 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-17117](https://insights.sbomify.com/CVE-2019-17117/): SQL injection in n/a (high 8.8)
- [CVE-2019-17120](https://insights.sbomify.com/CVE-2019-17120/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-17118 is a high-severity vulnerability in n/a, published on 17 Oct 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-17118 in the wild and no public exploit code.

Affected product: n/a. 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-17118/ (Markdown: https://insights.sbomify.com/CVE-2019-17118/index.md)
```

## Sources

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

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