# CVE-2023-5672: WP Mail Log < 1.1.3 – Contributor+ LFI in wml_logs/send_mail endpoint

> A contributor can exploit a path traversal flaw in the WP Mail Log plugin to read arbitrary files from the server.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 26 Dec 2023
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-pq3w-qg2x-wx83

## What is CVE-2023-5672?

CVE-2023-5672 is a medium-severity path traversal vulnerability in Unknown WP Mail Log, published on 26 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Mail Log WordPress plugin before 1.1.3 does not properly validate file path parameters when attaching files to emails, leading to local file inclusion, and allowing an attacker to leak the contents of arbitrary files.

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

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

It affects 1 product.


Products: Wpvibes Wp Mail Log.

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

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

## Is CVE-2023-5672 being exploited?

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

## Other vulnerabilities in Unknown WP Mail Log

- [CVE-2023-51410](https://insights.sbomify.com/CVE-2023-51410/): WordPress WP Mail Log Plugin <= 1.1.2 is vulnerable to Arbitrary File Upload (critical 9.9)
- [CVE-2023-5645](https://insights.sbomify.com/CVE-2023-5645/): WP Mail Log < 1.1.3 – Contributor+ SQL Injection in wml_logs endpoint (high 8.8)
- [CVE-2023-5673](https://insights.sbomify.com/CVE-2023-5673/): WP Mail Log < 1.1.3 – Contributor+ Arbitrary File Upload to RCE (high 8.8)
- [CVE-2023-5674](https://insights.sbomify.com/CVE-2023-5674/): WP Mail Log < 1.1.3 – Contributor+ SQL Injection in wml_logs/send_mail endpoint (high 8.8)
- [CVE-2023-5644](https://insights.sbomify.com/CVE-2023-5644/): WP Mail Log < 1.1.3 – Incorrect Authorization in REST API Endpoints (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5672 is a medium-severity path traversal vulnerability in Unknown WP Mail Log, published on 26 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5672 exists.

Affected product: Unknown WP Mail Log. 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-5672/ (Markdown: https://insights.sbomify.com/CVE-2023-5672/index.md)
```

## Sources

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

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