# CVE-2023-3178: POST SMTP Mailer < 2.5.7 - Arbitrary Log Deletion via CSRF

> Attackers can trick authenticated users into deleting arbitrary logs via CSRF in the POST SMTP Mailer WordPress plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Jan 2024
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-vv37-8w95-rgj3

## What is CVE-2023-3178?

CVE-2023-3178 is a medium-severity vulnerability in Unknown POST SMTP Mailer, published on 16 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The POST SMTP Mailer WordPress plugin before 2.5.7 does not have proper CSRF checks in some AJAX actions, which could allow attackers to make logged in users with the manage_postman_smtp capability delete arbitrary logs via a CSRF attack.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Wpexperts Post Smtp.

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

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

## Is CVE-2023-3178 being exploited?

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

## Other vulnerabilities in Unknown POST SMTP Mailer

- [CVE-2023-6875](https://insights.sbomify.com/CVE-2023-6875/): Auth bypass in Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App (critical 9.8)
- [CVE-2023-3179](https://insights.sbomify.com/CVE-2023-3179/): POST SMTP Mailer < 2.5.7 - Account Takeover via CSRF (high 8.8)
- [CVE-2023-52233](https://insights.sbomify.com/CVE-2023-52233/): WordPress POST SMTP Mailer plugin <= 2.8.6 - Broken Access Control on API vulnerability (high 8.6)
- [CVE-2024-52436](https://insights.sbomify.com/CVE-2024-52436/): WordPress Post SMTP plugin <= 2.9.9 - SQL Injection vulnerability (high 7.6)
- [CVE-2025-0521](https://insights.sbomify.com/CVE-2025-0521/): Post SMTP <= 3.0.2 - Unauthenticated Stored Cross-Site Scripting (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-3178 is a medium-severity vulnerability in Unknown POST SMTP Mailer, published on 16 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3178 exists.

Affected product: Unknown POST SMTP Mailer. 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-3178/ (Markdown: https://insights.sbomify.com/CVE-2023-3178/index.md)
```

## Sources

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

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