# CVE-2023-39286: Cross-site request forgery in n/a

> An unauthenticated attacker can perform CSRF attacks to modify system configuration settings on Mitel MiVoice Connect routers.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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:** 14 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-rw4j-5fjh-7xjp

## What is CVE-2023-39286?

CVE-2023-39286 is a medium-severity vulnerability in n/a, published on 14 Sep 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

A vulnerability in the Connect Mobility Router component of Mitel MiVoice Connect through 9.6.2304.102 could allow an unauthenticated attacker to perform a Cross Site Request Forgery (CSRF) attack due to insufficient request validation. A successful exploit could allow an attacker to provide a modified URL, potentially enabling them to modify system configuration settings.

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

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

It affects 1 product.


Products: Mitel Connect Mobility Router.

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

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

## Is CVE-2023-39286 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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