# CVE-2023-39933: File upload in pmc.exe

> Attackers can upload malicious files to the mail server to execute arbitrary code with web server privileges.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 18 Mar 2024
- **Updated:** 7 Nov 2024
- **Also known as:** GHSA-qgvx-mvf3-xw8r

## What is CVE-2023-39933?

CVE-2023-39933 is a medium-severity vulnerability in A.K.I Software  pmc.exe, published on 18 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Insufficient verification vulnerability exists in Broadcast Mail CGI (pmc.exe) included in A.K.I Software's PMailServer/PMailServer2 products. If this vulnerability is exploited, a user who can upload files through the product may execute an arbitrary executable file with the web server's execution privilege.

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

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


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

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

## Is CVE-2023-39933 being exploited?

There is no known exploitation of CVE-2023-39933 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39933 is a medium-severity vulnerability in A.K.I Software  pmc.exe, published on 18 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-39933 in the wild and no public exploit code.

Affected product: A.K.I Software  pmc.exe. 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-39933/ (Markdown: https://insights.sbomify.com/CVE-2023-39933/index.md)
```

## Sources

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

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