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

> Remote attackers can perform unauthorized actions like deleting users via CSRF in Infinias Access Control if a privileged user visits a malicious link.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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:** 14 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gr55-p5vp-c87j

## What is CVE-2019-18651?

CVE-2019-18651 is a medium-severity vulnerability in n/a, published on 14 Nov 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 cross-site request forgery (CSRF) vulnerability in 3xLogic Infinias Access Control through 6.6.9586.0 allows remote attackers to execute malicious and unauthorized actions (e.g., delete application users) by sending a crafted HTML document or encoded URL to a user that the website trusts. The user needs to have an active privileged session.

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

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

It affects 1 product.


Products: 3xlogic Infinias Access Control Firmware.

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

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

## Is CVE-2019-18651 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-18651 is a medium-severity vulnerability in n/a, published on 14 Nov 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-18651 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-18651/ (Markdown: https://insights.sbomify.com/CVE-2019-18651/index.md)
```

## Sources

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

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