Is SMTP Mail safe to use?

Laskyr does not give safety verdicts. SMTP Mail is closed on wordpress.org. Closed on 2025-12-31 (reason given: Guideline Violation). Closed plugins get no updates through WordPress, so new security holes will not be fixed for you. Keep SMTP Mail on the latest version and remove it if you do not use it.

Which versions of SMTP Mail are vulnerable?

Known issues on record (newest first): Cross-site request forgery (CSRF) (1.3.51 and older); Cross-site request forgery (CSRF) (1.3.20 and older); Stored cross-site scripting (XSS) (1.3.46 and older). The full list with sources is on this page.

What should I do if my SMTP Mail is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update smtp-mail). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · smtp-mail · data as of 2026-11-04

Is SMTP Mail safe? Known vulnerabilities and latest version

Status: Closed 2025-12-31
Known issues on record: 3
Unpatched in latest: 0

What to do

Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate smtp-mail && wp plugin delete smtp-mail

Check your version

Known vulnerabilities

3 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 3 record(s) do not state which versions are affected.

medium 4.3 CVE-2025-62762 · published 2025-12-09

Cross-site request forgery (CSRF) in SMTP Mail (1.3.51 and older)

Affected: 1.3.51 and older
Fixed in: unknown
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in photoboxone SMTP Mail smtp-mail allows Cross Site Request Forgery.This issue affects SMTP Mail: from n/a through <= 1.3.51.

NVD CVE-2025-62762 Patchstack advisory

high 8.8 CVE-2024-25914 · published 2024-02-13

Cross-site request forgery (CSRF) in SMTP Mail (1.3.20 and older)

Affected: 1.3.20 and older
Fixed in: unknown
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in Photoboxone SMTP Mail.This issue affects SMTP Mail: from n/a through 1.3.20.

NVD CVE-2024-25914 Patchstack advisory

medium 6.1 CVE-2023-3092 · published 2023-07-12

Stored cross-site scripting (XSS) in SMTP Mail (1.3.46 and older)

Affected: 1.3.46 and older
Fixed in: unknown
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

The SMTP Mail plugin for WordPress is vulnerable to Stored Cross-Site Scripting via an email subject in versions up to, and including, 1.3.46 due to insufficient input sanitization and output escaping when the 'Save Data SendMail' feature is enabled. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

NVD CVE-2023-3092 Wordfence advisory Plugin source

Recent activity

2025-12-31 — closed on wordpress.org (Guideline Violation).
2025-12-09 — Cross-site request forgery (CSRF) disclosed (CVE-2025-62762), fix version not stated.
2024-02-13 — Cross-site request forgery (CSRF) disclosed (CVE-2024-25914), fix version not stated.
2023-07-12 — Stored cross-site scripting (XSS) disclosed (CVE-2023-3092), fix version not stated.

Free. We check the CVE feeds every day and email you only when a new issue for SMTP Mail (smtp-mail) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site request forgery (CSRF) (2) · Cross-site scripting (XSS) (1)

Where this data comes from

Version, last update, installs, closure: wordpress.org/plugins/smtp-mail (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/smtp-mail"><img src="https://laskyr.com/plugins/smtp-mail/badge.svg" alt="SMTP Mail vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is SMTP Mail safe? Known vulnerabilities and latest version

SMTP Mail is closed on wordpress.org

What to do

Check your version

Known vulnerabilities

Cross-site request forgery (CSRF) in SMTP Mail (1.3.51 and older)

Cross-site request forgery (CSRF) in SMTP Mail (1.3.20 and older)

Stored cross-site scripting (XSS) in SMTP Mail (1.3.46 and older)

Recent activity

Get an email when SMTP Mail has a new vulnerability

Browse vulnerabilities

Where this data comes from