# CVE-2023-32616: Use after free in Foxit Reader

> A use-after-free in Foxit Reader allows arbitrary code execution via malicious PDFs or websites, requiring user interaction.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Nov 2023
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-pjgh-f3xj-rv83

## What is CVE-2023-32616?

CVE-2023-32616 is a high-severity use after free vulnerability in Foxitsoftware Foxit Reader, published on 27 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A use-after-free vulnerability exists in the way Foxit Reader 12.1.2.15356 handles 3D annotations. A specially crafted Javascript code inside a malicious PDF document can trigger reuse of a previously freed object, which can lead to memory corruption and result in arbitrary code execution. An attacker needs to trick the user into opening the malicious file to trigger this vulnerability. Exploitation is also possible if a user visits a specially crafted, malicious site if the browser plugin extension is enabled.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Foxitsoftware Foxit Reader.

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

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

## Is CVE-2023-32616 being exploited?

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

## Other vulnerabilities in Foxitsoftware Foxit Reader

- [CVE-2021-33793](https://insights.sbomify.com/CVE-2021-33793/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-38568](https://insights.sbomify.com/CVE-2021-38568/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-38572](https://insights.sbomify.com/CVE-2021-38572/): Path traversal in n/a (critical 9.8)
- [CVE-2021-38573](https://insights.sbomify.com/CVE-2021-38573/): Path traversal in n/a (critical 9.8)
- [CVE-2021-38574](https://insights.sbomify.com/CVE-2021-38574/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32616 is a high-severity use after free vulnerability in Foxitsoftware Foxit Reader, published on 27 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-32616 in the wild and no public exploit code.

Affected product: Foxitsoftware Foxit Reader. 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-32616/ (Markdown: https://insights.sbomify.com/CVE-2023-32616/index.md)
```

## Sources

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

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