CVE-2026-2471 HIGH

CVE-2026-2471: WP Mail Logging <= 1.15.0 - Unauthenticated PHP Object Injection via Email Log Message Field

Vendor Smub
Product WP Mail Logging
Weakness CWE-502 · Unsafe deserialization
Published February 28, 2026
Last update April 8, 2026

CVSS base score

7.5/10
Attack vector Network
Attack complexity High
Privileges required None
User interaction Required
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

WP Mail Logging versions up to 1.15.0 contain a deserialization vulnerability that allows attackers to execute arbitrary code on affected WordPress sites. An attacker can craft a malicious serialized object that, when deserialized by the plugin, executes PHP code with site privileges. The attack requires user interaction—typically tricking a site administrator into visiting a malicious link or page.

What an attacker can do

03Attacker Capabilities

Run arbitrary PHP code on the WordPress site with the privileges of the web server.

Potential impact on your site

04Site Impact

An attacker can compromise your entire WordPress installation, steal data, modify content, or install backdoors.

Conditions required to exploit

05Prerequisites

No authentication required, but the victim must click a malicious link or visit an attacker-controlled page.

Key dates

06Disclosure timeline

February 28, 2026 CVE published
April 8, 2026 Record updated