CVE-2026-57657

Gmail SMTP <= 1.2.3.19 - Cross-Site Request Forgery

2026-06-26 00:00
Ananda Dhakal

Strategic Overview

Status
Patched in 1.2.3.20
Affected Plugin
Gmail SMTP
Affected Version
<= 1.2.3.19
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-57657
View all Gmail SMTP vulnerabilities

At a glance

CVE-2026-57657 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Gmail SMTP WordPress plugin, affecting versions <= 1.2.3.19. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.3.20; sites on affected versions should update now. Disclosed June 2026, reported by Ananda Dhakal.

Vulnerability Overview

The Gmail SMTP plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.2.3.19. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

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

Reaching this weakness in Gmail SMTP <= 1.2.3.19 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Gmail SMTP the fix is 1.2.3.20: builds <= 1.2.3.19 are affected, anything from 1.2.3.20 onward is not.

Remediation

Update to version 1.2.3.20, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Gmail SMTP: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Gmail SMTP 1.2.3.20 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C