# CVE-2023-49233: Missing authorization in n/a

> Attackers with non-admin accounts can access admin functions to steal credentials and escalate privileges in Visual Planning Admin Center.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2024
- **Updated:** 24 Oct 2024
- **Also known as:** GHSA-j3v3-2jrv-w8cx

## What is CVE-2023-49233?

CVE-2023-49233 is a high-severity missing authorization vulnerability in n/a, published on 3 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Insufficient access checks in Visual Planning Admin Center 8 before v.1 Build 240207 allow attackers in possession of a non-administrative Visual Planning account to utilize functions normally reserved for administrators. The affected functions allow attackers to obtain different types of configured credentials and potentially elevate their privileges to administrator level.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2023-49233 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-49233 is a high-severity missing authorization vulnerability in n/a, published on 3 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49233 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-49233/ (Markdown: https://insights.sbomify.com/CVE-2023-49233/index.md)
```

## Sources

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

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