# CVE-2023-40827: pf4j vulnerable to remote code execution via loadpluginPath parameter

> A remote attacker can exploit a path traversal vulnerability in pf4j to execute arbitrary code and access sensitive information.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2023
- **Updated:** 2 Oct 2024
- **Also known as:** DEBIAN-CVE-2023-40827, GHSA-rvm8-j2cp-j592, UBUNTU-CVE-2023-40827

## What is CVE-2023-40827?

CVE-2023-40827 is a high-severity path traversal vulnerability in n/a, published on 28 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in pf4j pf4j v.3.9.0 and before allows a remote attacker to obtain sensitive information and execute arbitrary code via the loadpluginPath parameter.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

2 open source packages ship an affected version, including org.pf4j:pf4j. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.pf4j:pf4j` | Maven | All versions to 3.9.0 | None |
| `org.pf4j:pf4j` | Maven | All versions to 3.9.0 | None |

Products: Pf4j Project Pf4j.

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

Upgrade to a fixed version.

## Is CVE-2023-40827 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-70952](https://insights.sbomify.com/CVE-2025-70952/): pf4j is vulnerable to Path Traversal or Zip Slip attack through improper handling of zip entry names (high 7.5)
- [CVE-2023-40826](https://insights.sbomify.com/CVE-2023-40826/): pf4j vulnerable to remote code execution via the zippluginPath parameter (high 7.5)
- [CVE-2023-40828](https://insights.sbomify.com/CVE-2023-40828/): pf4j vulnerable to remote code execution via expandIfZip method in the extract function (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-40827 is a high-severity path traversal vulnerability in n/a, published on 28 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-40827 exists.

Affected packages and fixed versions:
- org.pf4j:pf4j (Maven): affected all versions up to 3.9.0; no fix listed
- org.pf4j:pf4j (Maven): affected all versions up to 3.9.0; no fix listed

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

## Sources

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

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