CVE-2025-24739

FluentSMTP <= 2.2.80 - Cross-Site Request Forgery

2025-01-24 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 2.2.81
Affected Plugin
FluentSMTP – WP Mail SMTP Plugin with Amazon SES, SendGrid, Mailgun, Postmark, Cloudflare, toSend, Gmail and Any SMTP
Affected Version
<= 2.2.80
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-24739
View all FluentSMTP – WP Mail SMTP Plugin with Amazon SES, SendGrid, Mailgun, Postmark, Cloudflare, toSend, Gmail and Any SMTP vulnerabilities

At a glance

CVE-2025-24739 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the FluentSMTP WordPress plugin, affecting versions <= 2.2.80. 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 2.2.81; sites on affected versions should update now. Disclosed January 2025, reported by Rafie Muhammad.

Vulnerability Overview

The FluentSMTP plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.2.80. 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 FluentSMTP <= 2.2.80 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 FluentSMTP the fix is 2.2.81: builds <= 2.2.80 are affected, anything from 2.2.81 onward is not.

Remediation

Update to version 2.2.81, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-24739https://www.wordfence.com/threat-intel/vulnerabilities/id/33a801ab-b86f-42b3-bb79-dad64617a56ahttps://nvd.nist.gov/vuln/detail/CVE-2025-24739

Related records

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