# CVE-2023-32792: Cross-Site Request Forgery on NXLog Manager

> An attacker can eliminate roles in NXLog Manager via CSRF due to missing origin validation, requiring user interaction to modify platform configuration.

- **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:** 3 Oct 2023
- **Updated:** 5 Sep 2024
- **Also known as:** GHSA-2jpg-9jfq-36cj

## What is CVE-2023-32792?

CVE-2023-32792 is a medium-severity vulnerability in NXLog Manager, published on 3 Oct 2023. 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

Cross-Site Request Forgery (CSRF) vulnerability in NXLog Manager 5.6.5633 version. This vulnerability allows an attacker to eliminate roles within the platform by sending a specifically crafted query to the server. The vulnerability is based on the absence of proper validation of the origin of incoming requests.

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

## Which versions are affected by CVE-2023-32792?

It affects 1 product.


Products: Nxlog Nxlog Manager.

## How do I fix CVE-2023-32792?

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

## Is CVE-2023-32792 being exploited?

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

## Other vulnerabilities in NXLog Manager

- [CVE-2023-32791](https://insights.sbomify.com/CVE-2023-32791/): Cross-Site Request Forgery on NXLog Manager (medium 6.5)
- [CVE-2023-32790](https://insights.sbomify.com/CVE-2023-32790/): XSS on NXLog Manager (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32792 and fix it if it is affected.

What it is: CVE-2023-32792 is a medium-severity vulnerability in NXLog Manager, published on 3 Oct 2023. 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-2023-32792 in the wild and no public exploit code.

Affected product: NXLog Manager. 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-2023-32792/ (Markdown: https://insights.sbomify.com/CVE-2023-32792/index.md)
```

## Sources

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

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