# CVE-2023-39345: Unauthorized Access to Private Fields in User Registration API in strapi

> Attackers can modify private user fields during registration, potentially escalating privileges or altering account data in Strapi CMS.

- **Severity:** High 7.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Nov 2023
- **Updated:** 4 Sep 2024
- **Also known as:** GHSA-gc7p-j5xm-xxh2

## What is CVE-2023-39345?

CVE-2023-39345 is a high-severity missing authorization vulnerability in strapi, published on 6 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

strapi is an open-source headless CMS. Versions prior to 4.13.1 did not properly restrict write access to fielded marked as private in the user registration endpoint. As such malicious users may be able to errantly modify their user records. This issue has been addressed in version 4.13.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-287 (Improper Authentication)

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

4 open source packages ship an affected version, including @strapi/plugin-users-permissions and @strapi/strapi. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@strapi/plugin-users-permissions` | npm | From 4.0.0 | 4.13.1 |
| `@strapi/plugin-users-permissions` | npm | From 4.0.0 | 4.13.1 |
| `@strapi/strapi` | npm | From 4.0.0 | 4.13.1 |
| `@strapi/strapi` | npm | From 4.0.0 | 4.13.1 |

Products: Strapi Strapi.

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

Upgrade @strapi/plugin-users-permissions to 4.13.1 or later.

## Is CVE-2023-39345 being exploited?

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

## Other vulnerabilities in strapi

- [CVE-2023-22894](https://insights.sbomify.com/CVE-2023-22894/): Strapi Cleartext Storage of Sensitive Information (high 7.2, exploited in the wild)
- [CVE-2023-22621](https://insights.sbomify.com/CVE-2023-22621/): Strapi plugins vulnerable to Server-Side Template Injection and Remote Code Execution in the Users-Permissions Plugin (critical 10.0)
- [CVE-2022-27263](https://insights.sbomify.com/CVE-2022-27263/): Unrestricted Upload of File with Dangerous Type in Strapi (critical 9.8)
- [CVE-2020-27664](https://insights.sbomify.com/CVE-2020-27664/): Authorization bypass in Strapi (critical 9.8)
- [CVE-2019-18818](https://insights.sbomify.com/CVE-2019-18818/): Strapi allows unauthenticated attacker to reset admin password without valid reset token (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39345 is a high-severity missing authorization vulnerability in strapi, published on 6 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-39345 exists.

Affected packages and fixed versions:
- @strapi/plugin-users-permissions (npm): affected from 4.0.0; fixed in 4.13.1
- @strapi/plugin-users-permissions (npm): affected from 4.0.0; fixed in 4.13.1
- @strapi/strapi (npm): affected from 4.0.0; fixed in 4.13.1
- @strapi/strapi (npm): affected from 4.0.0; fixed in 4.13.1

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

## Sources

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

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