FluentSMTP vulnerabilities: the records, and where its mail secrets and email log sit
FluentSMTP hands WordPress email to the mail services you connect and can log every message.
Some record titles filed under it name the email logs, the email subject and a recipient display name. Hold the installed version against every range, then read where each connection keeps its secret and how long the log lasts.
On this page
FluentSMTP vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 6 records for FluentSMTP. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 2.3.0
Worked out from data retrieved on .
Every affected range listed in this source for FluentSMTP ends before version 2.3.0.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
FluentSMTP <= 2.2.95 - Unauthenticated Stored Cross-Site Scripting via Recipient Display Name (to.name) in Email Logs
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2026-16636
Affected versions- All versions up to and including 2.2.95
Patched versions: 2.3.0
Update to at least version 2.3.0.
FluentSMTP <= 2.2.80 - Cross-Site Request Forgery
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2025-24739
Affected versions- All versions up to and including 2.2.80
Patched versions: 2.2.81
Update to at least version 2.2.81.
FluentSMTP - WP SMTP Plugin with Amazon SES, SendGrid, MailGun, Postmark, Google and Any SMTP Provider <= 2.2.82 - Unauthenticated PHP Object Injection
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.8)
- CVE:
- CVE-2024-9511
Affected versions- All versions up to and including 2.2.82
Patched versions: 2.2.83
Update to at least version 2.2.83.
FluentSMTP <= 2.2.4 - Unauthenticated Stored Cross-Site Scripting via Email Subject
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2023-3087
Affected versions- All versions up to and including 2.2.4
Patched versions: 2.2.5
Update to at least version 2.2.5.
FluentSMTP <= 2.2.2 - Authenticated (Author+) Stored Cross-Site Scripting via Email Logs
- Published:
- Last updated:
- Severity:
- Low (CVSS 3.8)
- CVE:
- CVE-2023-0219
Affected versions- All versions up to and including 2.2.2
Patched versions: 2.2.3
Update to at least version 2.2.3.
Show 1 older recordHide the older record
FluentSMTP <= 2.0.0 - Authenticated (Admin+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.5)
- CVE:
- CVE-2021-24528
Affected versions- All versions before 2.0.1
Patched versions: 2.0.1
Update to at least version 2.0.1.
Check FluentSMTP on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
FluentSMTP's connections, secrets and log of sent mail
The WordPress.org listing for FluentSMTP says it replaces the WordPress wp_mail() function and hands every email to the service you connected, using that service's own API where one exists, or the SMTP host, port and credentials you gave it for a plain SMTP connection.
Its installation steps open it from Settings > FluentSMTP. The vendor's dashboard guide says the General Settings there include logging and how long logs are kept, and that Alerts is where failure notifications and the summary email live.
The listing says FluentSMTP logs every email your WordPress site sends, and its feature list includes "Email logging with full headers, body and server response". It also says every plugin and theme that sends email through wp_mail() is covered. A message a form or shop plugin sends can therefore end up in that log.
WordPress documents the Administrator role as having access to every administration feature on a single site, and a changelog entry adds the fluent_mail/manage_capability filter "to change the required admin capability".
FluentSMTP security records: email fields, a forged request and object injection
Stored cross-site scripting recurs, and these titles name the email logs, the email subject or a recipient display name.
CVE-2026-16636 has a title ending "Unauthenticated Stored Cross-Site Scripting via Recipient Display Name (to.name) in Email Logs" (affected: all versions up to and including 2.2.95; patched: 2.3.0). CVE-2023-3087's title ends "Unauthenticated Stored Cross-Site Scripting via Email Subject" (affected: all versions up to and including 2.2.4; patched: 2.2.5). CVE-2023-0219's title ends "Authenticated (Author+) Stored Cross-Site Scripting via Email Logs" (affected: all versions up to and including 2.2.2; patched: 2.2.3).
CVE-2024-9511, which the source data rates Critical (CVSS 9.8), has a title ending "Unauthenticated PHP Object Injection" (affected: all versions up to and including 2.2.82; patched: 2.2.83). CVE-2025-24739's title ends "Cross-Site Request Forgery" (affected: all versions up to and including 2.2.80; patched: 2.2.81). CVE-2021-24528's title ends "Authenticated (Admin+) Stored Cross-Site Scripting", and its fields list all versions before 2.0.1, with 2.0.1 patched.
The ranges overlap. 2.2.81, patched for CVE-2025-24739, lies within CVE-2024-9511's affected range, and the range of CVE-2026-16636 takes in the patched version of every other record named here. Check the installed number against each affected range in the history on this page before reading the update guidance at the top of the history.
For CVE-2026-16636 the affected range ends at 2.2.95 and the patched version is 2.3.0: the fields say nothing about the versions between the two, so for that record the patched version is the one to reach.
Entries beginning "Security:" in FluentSMTP's WordPress.org changelog mark some fixes in the vendor's own words. Read them beside the history before an update.
Reading FluentSMTP's settings without sending mail
Each check is a reading, made on a site whose owner has authorised the review.
Leave every form unsaved. The dashboard guide puts a "Send Test Email" button on the right of the FluentSMTP top bar, and the listing says the wp fluent-smtp test command sends a test email through any connection. Leave both alone.
Read FluentSMTP's row on the Plugins screen. WordPress documents a version number inside the Description column there, and an update notice once the Plugin Directory has a newer version of a plugin it hosts. Write down both, and what its "Automatic update" column shows.
The settings guide puts "Active Email Connections" on the left of Settings in the FluentSMTP top bar. For each row, write down the provider and From address, then open its Edit pencil and note the storage option selected, without copying or revealing any key or password the form shows.
The guide describes three: "Store in Database", the default, where FluentSMTP encrypts the key or password with your WordPress SALT keys before saving it; the same with "Disable Encryption" ticked, which it says stores the secret as readable text; and "Store in wp-config.php", where the form shows define() lines in place of key fields.
The listing's FAQ says the vendor recommends wp-config.php, while the settings guide says to leave "Store in Database" selected and that most sites should stop there.
Record the option, never what a key or password field holds, and leave without pressing "Save Connection Settings", which the Other SMTP guide says makes FluentSMTP try the server. Where "Store in wp-config.php" is selected, the settings guide calls the form the source of truth for the constant names, such as FLUENTMAIL_SMTP_PASSWORD for Other SMTP. Note the names the form shows, never a value.
Under "General Settings" on the same screen, record whether "Log Emails" is on, which the settings guide gives as the default, and the "Delete Logs" period, whose options it says run from 7 days to 2 years. Record "Email Simulation" too, which the guide says stops delivery but keeps writing messages to the log, and which it says does nothing when FLUENTMAIL_SIMULATE_EMAILS is defined in PHP.
The email logs guide says opening a logged message shows its body, headers, attachments and server response. On "Email Logs", note whether entries exist and the date of the oldest, without opening any, and leave Resend, Delete and any "Turn On" offer alone.
For who can read them, start with everyone listed under the Users screen's Administrator filter link, name the person behind each account, and ask the developer whether any code uses the fluent_mail/manage_capability filter.
The routing guide says mail sent from a connection's own From address always goes through that connection, and everything else through the Default, then the Fallback if that fails. Write down which row carries the "Default" mark, and any "+N senders" mark on an Amazon SES or toSend row, which the guide ties to extra From addresses on one connection.
The settings guide puts "Force From Email" on each connection form, under "Sender Settings", and says Gmail, Outlook and Cloudflare do not show it.
It says the option sends any mail not already routed to another connection from that address, whatever From the sending plugin set. Read it on each form.
Record which row carries the "Fallback" mark, or that none does, reading the row itself and leaving its Actions menu closed. The settings guide says a Fallback cannot be set until there is more than one connection, and the routing guide says it runs when the Default's send fails, naming API error, auth and timeout.
Then open Alerts, where the dashboard guide says failure notifications and the summary email live. Write down each channel set up and where it posts; the Slack guide says a connected row shows the workspace and channel as Connected. Under "Summary Email", record "Enable Email Summary" and the "Send To" addresses, leaving Set Up, Disconnect and "Save Settings" untouched.
What a FluentSMTP version match leaves open
A FluentSMTP version outside every range cannot show a secret stored as readable text, how long the log keeps message bodies, where the Fallback and alerts point, or whether code has changed the required admin capability through fluent_mail/manage_capability.
Inside a range, the match ties the version to a known record; it does not show that the site was attacked.
A WordPress security audit records every installed plugin, active or not, with its version and whether automatic updates are on. Deactivated plugins stay on that list, so a WP Mail SMTP copy deactivated at the end of the listing's migration steps would be on it too. Among its password reset checks, the audit finds any email log and confirms that reading it is limited to administrators.
Frequently asked questions
Each record carries its own range: CVE-2026-16636 lists all versions up to and including 2.2.95, with 2.3.0 patched, and CVE-2021-24528 all versions before 2.0.1, with 2.0.1 patched. Match the installed version against every range before relying on the update guidance at the top of the history.
The listing says there is no pro version, no premium add-ons and no paid tier, and that every provider and every feature is in the free plugin. The records on this page are the ones the source data files under the fluent-smtp slug, CVE-2024-9511 among them, though its title opens with a longer form of the plugin's name.
The listing describes email logging with full headers, body and server response, kept in the plugin's own database table. The settings guide says "Log Emails" is on by default and gives "Delete Logs" options from 7 days to 2 years. With logging switched off, the listing says only failed emails are recorded.
In the listing's migration steps, FluentSMTP detects an existing WP Mail SMTP by WPForms configuration, you import it with the "Import From WP Mail SMTP" button, and the last step is to deactivate the old plugin. Look for it on the Plugins screen, and read the imported connection's storage option. WordPress's hardening guide advises deleting plugins that are not being used.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to every record listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- FluentSMTP <= 2.2.95 - Unauthenticated Stored Cross-Site Scripting via Recipient Display Name (to.name) in Email Logs (CVE-2026-16636)
- FluentSMTP <= 2.2.80 - Cross-Site Request Forgery (CVE-2025-24739)
- FluentSMTP - WP SMTP Plugin with Amazon SES, SendGrid, MailGun, Postmark, Google and Any SMTP Provider <= 2.2.82 - Unauthenticated PHP Object Injection (CVE-2024-9511)
- FluentSMTP <= 2.2.4 - Unauthenticated Stored Cross-Site Scripting via Email Subject (CVE-2023-3087)
- FluentSMTP <= 2.2.2 - Authenticated (Author+) Stored Cross-Site Scripting via Email Logs (CVE-2023-0219)
- FluentSMTP <= 2.0.0 - Authenticated (Admin+) Stored Cross-Site Scripting (CVE-2021-24528)