# CVE-2023-49231: Auth bypass in n/a

> An unauthenticated attacker can obtain an administrative API token in Stilog Visual Planning, leading to full system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 29 Mar 2024
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-vpp6-9fcm-rv58

## What is CVE-2023-49231?

CVE-2023-49231 is a critical authentication bypass vulnerability in n/a, published on 29 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability was found in Stilog Visual Planning 8. It allows an unauthenticated attacker to receive an administrative API token.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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


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

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

## Is CVE-2023-49231 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49231 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-49231 is a critical authentication bypass vulnerability in n/a, published on 29 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49231 exists.

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-49231/ (Markdown: https://insights.sbomify.com/CVE-2023-49231/index.md)
```

## Sources

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

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