# CVE-2023-4536: My Account Page Editor < 1.3.2 - Subscriber+ Arbitrary File Upload

> Authenticated users can upload arbitrary files to the server, leading to remote code execution.

- **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:** 16 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-5qx2-wfg4-53mm

## What is CVE-2023-4536?

CVE-2023-4536 is a high-severity vulnerability in Unknown My Account Page Editor, published on 16 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The My Account Page Editor WordPress plugin before 1.3.2 does not validate the profile picture to be uploaded, allowing any authenticated users, such as subscriber to upload arbitrary files to the server, leading to RCE

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Koalaapps My Account Page Editor.

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

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

## Is CVE-2023-4536 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4536 is a high-severity vulnerability in Unknown My Account Page Editor, published on 16 Jan 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-4536 exists.

Affected product: Unknown My Account Page Editor. 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-4536/ (Markdown: https://insights.sbomify.com/CVE-2023-4536/index.md)
```

## Sources

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

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