HomeWordPress vulnerabilitiesWP Mail Logging
WP Mail Logging vulnerabilities
WP Mail Logging has 3 known vulnerabilities in this database. The most recent published record is dated 2 Oct 2026.
- Known vulnerabilities
- 3
- Active installs
- 300,000+
- Latest version
- 1.17.0
- Last updated
- 21 Sep 2026
- Most recent
- 2 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Content injection CVE-2026-1661 | Medium 4.3 | Before 1.17.0 | Fixed in 1.17.0 | 5 d ago |
| PHP object injection CVE-2026-2471 | High 7.5 | Up to 1.15.0 | Fixed in a later version (latest 1.17.0) | 28 Feb 2026 |
| Cross-site scripting (XSS) CVE-2023-3081 | High 7.2 | Before 1.11.2 | Fixed in 1.11.2 | 12 Jul 2023 |
Read the published descriptions
- CVE-2026-1661, 2 Oct 2026
- The WP Mail Logging WordPress plugin before 1.17.0 does not properly restrict the HTML and CSS of logged emails before rendering them in its admin log screens, allowing unauthenticated users to inject styled content and links, for example through a public contact form, that can deceive an administrator viewing the log and send their browser to an attacker-controlled page. CVE record
- CVE-2026-2471, 28 Feb 2026
- The WP Mail Logging plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.15.0 via deserialization of untrusted input from the email log message field. This is due to the `BaseModel` class constructor calling `maybe_unserialize()` on all properties retrieved from the database without validation. This makes it possible for unauthenticated attackers to inject a PHP Object by submitting a double-serialized payload through any public-facing form that sends email (e.g., Contact Form 7). When the email is logged and subsequently viewed by an administrator, the malicious payload is deserialized into an arbitrary PHP object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present. CVE record
- CVE-2023-3081, 12 Jul 2023
- The WP Mail Logging plugin for WordPress is vulnerable to Stored Cross-Site Scripting via email contents in versions up to, and including, 1.11.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Note: An incomplete fix was released in 1.11.1. CVE record
What to do if you run WP Mail Logging
If you run WP Mail Logging, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP Mail Logging vulnerabilities
Free. We email you when a new vulnerability is published for WP Mail Logging, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.