# CVE-2023-42920: Other in FileMaker Pro

> Attackers can execute arbitrary code via dylib hijacking in FileMaker Pro on macOS, requiring users to update the application.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2024
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-fq86-8676-6j38

## What is CVE-2023-42920?

CVE-2023-42920 is a high-severity vulnerability in Claris FileMaker Pro, published on 19 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Claris International has fixed a dylib hijacking vulnerability in the FileMaker Pro.app and Claris Pro.app versions on macOS.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 2 products.


Products: Claris Claris Pro, Claris Filemaker Pro.

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

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

## Is CVE-2023-42920 being exploited?

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

## Other vulnerabilities in Claris FileMaker Pro

- [CVE-2023-42954](https://insights.sbomify.com/CVE-2023-42954/): Information disclosure in FileMaker Server (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-42920 is a high-severity vulnerability in Claris FileMaker Pro, published on 19 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-42920 in the wild and no public exploit code.

Affected product: Claris FileMaker Pro. 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-42920/ (Markdown: https://insights.sbomify.com/CVE-2023-42920/index.md)
```

## Sources

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

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