# CVE-2023-40160: Path traversal in pmmls.exe

> A remote attacker can exploit a directory traversal flaw in the Mailing List Search CGI to read arbitrary files on the server.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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:** No
- **Published:** 18 Mar 2024
- **Updated:** 24 Mar 2025
- **Also known as:** GHSA-27v4-w7r4-68vg

## What is CVE-2023-40160?

CVE-2023-40160 is a low-severity path traversal vulnerability in A.K.I Software  pmmls.exe, published on 18 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability exists in Mailing List Search CGI (pmmls.exe) included in A.K.I Software's PMailServer/PMailServer2 products. If this vulnerability is exploited, a remote attacker may obtain arbitrary files on the server.

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

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


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

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

## Is CVE-2023-40160 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-40160 is a low-severity path traversal vulnerability in A.K.I Software  pmmls.exe, published on 18 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-40160 in the wild and no public exploit code.

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

## Sources

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

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