# CVE-2023-36100: Privilege escalation in n/a

> Attackers can escalate privileges and access sensitive information via the UserID parameter in the ChangeUser API endpoint.

- **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:** 1 Sep 2023
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-4g5h-7prv-mvj5

## What is CVE-2023-36100?

CVE-2023-36100 is a critical vulnerability in n/a, published on 1 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in IceCMS version 2.0.1, allows attackers to escalate privileges and gain sensitive information via UserID parameter in api/User/ChangeUser.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Macwk Icecms.

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

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

## Is CVE-2023-36100 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-42188](https://insights.sbomify.com/CVE-2023-42188/): Cross-site request forgery in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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