Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2023-3179

CVE-2023-3179 - Before 2 Plugin

CVE-2023-3179

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

CVE-2023-3179

HIGH CVSS 8.8 Published 2023-07-17 Updated 2025-06-04
AI Risk High (78/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P2 Urgent
Severity Band HIGH
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected Components 3
Reference Links 1
AI Risk Engine High (78/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2023-07-17 CVE published and first recorded in the threat feed.
  2. 2025-06-04 Record updated with latest vulnerability metadata.
  3. 2026-04-09 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 6 days ago

AI enriched 6 days ago (2026-04-09 07:52 UTC)

Technical Summary

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

Potential Impact

Severity is HIGH (CVSS 8.8). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Before 2 PLUGIN · before-2 Affected: < 2.5.7 Fixed in: 2.5.7
Post Smtp PLUGIN · post-smtp Affected: < 2.5.7 Fixed in: 2.5.7
Post Smtp Mailer PLUGIN · post-smtp-mailer Affected: < 2.5.7 Fixed in: 2.5.7
Scroll to top