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

> Attackers can escalate privileges by assigning arbitrary roles to new external users, gaining access to all workspaces and data.

- **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:** 8 Jun 2023
- **Updated:** 6 Jan 2025
- **Also known as:** GHSA-rm22-vh4p-35m7

## What is CVE-2023-32749?

CVE-2023-32749 is a high-severity vulnerability in n/a, published on 8 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pydio Cells allows users by default to create so-called external users in order to share files with them. By modifying the HTTP request sent when creating such an external user, it is possible to assign the new user arbitrary roles. By assigning all roles to a newly created user, access to all cells and non-personal workspaces is granted.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Pydio Cells.

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

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

## Is CVE-2023-32749 being exploited?

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

Public exploit code:

- Exploit for CVE-2023-32749 affecting Pydio Cells 4.1.2 and earlier (github_poc): https://github.com/alaeddine03/CVE-2023-32749-PoC
- Pydio Cells 4.1.2 - Unauthorised Role Assignments (exploitdb)
- PoC for CVE-2023-32749 affecting Pydio Cells (github_poc): https://github.com/xcr-19/CVE-2023-32749

## Other vulnerabilities in n/a

- [CVE-2019-12901](https://insights.sbomify.com/CVE-2019-12901/): Path traversal in n/a (high 8.8)
- [CVE-2020-12851](https://insights.sbomify.com/CVE-2020-12851/): Path traversal in n/a (high 8.1)
- [CVE-2020-12847](https://insights.sbomify.com/CVE-2020-12847/): Command injection in n/a (high 7.2)
- [CVE-2020-12850](https://insights.sbomify.com/CVE-2020-12850/): The following vulnerability applies only to the Pydio Cells Enterprise OVF version 2.0.4. (high 7.0)
- [CVE-2020-12852](https://insights.sbomify.com/CVE-2020-12852/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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