# CVE-2023-32316: Users can add themselves to any organization in CloudExplorer Lite


- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 May 2023
- **Updated:** 14 Jan 2025
- **Also known as:** GHSA-cp3j-437h-4vwj

## What is CVE-2023-32316?

CVE-2023-32316 is a high-severity vulnerability in CloudExplorer-Dev CloudExplorer-Lite, published on 26 May 2023. 

### Official description

CloudExplorer Lite is an open source cloud management tool. In affected versions users can add themselves to any organization in CloudExplorer Lite. This is due to a missing permission check on the user profile. It is recommended to upgrade the version to v1.1.0. There are no known workarounds for this vulnerability.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Fit2cloud Cloudexplorer.

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

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

## Is CVE-2023-32316 being exploited?

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

## Other vulnerabilities in CloudExplorer-Dev CloudExplorer-Lite

- [CVE-2023-32311](https://insights.sbomify.com/CVE-2023-32311/): The CloudExplorer Lite missing permissions check (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32316 is a high-severity vulnerability in CloudExplorer-Dev CloudExplorer-Lite, published on 26 May 2023. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32316 exists.

Affected product: CloudExplorer-Dev CloudExplorer-Lite. 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-32316/ (Markdown: https://insights.sbomify.com/CVE-2023-32316/index.md)
```

## Sources

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

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