CVE-2026-2471: CWE-502 Deserialization of Untrusted Data in smub WP Mail Logging
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.
AI Analysis
Technical Summary
CVE-2026-2471 is a deserialization vulnerability in the WP Mail Logging WordPress plugin (versions up to 1.15.0). The issue arises because the BaseModel class constructor calls maybe_unserialize() on all database properties without validating the input, allowing unauthenticated attackers to inject PHP objects via double-serialized payloads submitted through email forms. Exploitation requires the presence of a PHP Object Injection POP chain in other installed plugins or themes to achieve impactful outcomes such as arbitrary file deletion, sensitive data access, or remote code execution.
Potential Impact
The vulnerability enables unauthenticated attackers to inject PHP objects into the plugin's email log data. However, without a PHP Object Injection POP chain in other installed components, this vulnerability has no direct impact. If a POP chain is present, attackers may perform high-impact actions including file deletion, data theft, or code execution, leading to confidentiality, integrity, and availability compromises.
Mitigation Recommendations
No official patch or fix is currently available for this vulnerability. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is released, administrators should consider disabling or restricting access to the WP Mail Logging plugin, especially limiting access to email logs to trusted users only. Additionally, review and minimize the installation of plugins or themes that may contain PHP Object Injection POP chains to reduce exploitation risk.
CVE-2026-2471: CWE-502 Deserialization of Untrusted Data in smub WP Mail Logging
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-2471 is a deserialization vulnerability in the WP Mail Logging WordPress plugin (versions up to 1.15.0). The issue arises because the BaseModel class constructor calls maybe_unserialize() on all database properties without validating the input, allowing unauthenticated attackers to inject PHP objects via double-serialized payloads submitted through email forms. Exploitation requires the presence of a PHP Object Injection POP chain in other installed plugins or themes to achieve impactful outcomes such as arbitrary file deletion, sensitive data access, or remote code execution.
Potential Impact
The vulnerability enables unauthenticated attackers to inject PHP objects into the plugin's email log data. However, without a PHP Object Injection POP chain in other installed components, this vulnerability has no direct impact. If a POP chain is present, attackers may perform high-impact actions including file deletion, data theft, or code execution, leading to confidentiality, integrity, and availability compromises.
Mitigation Recommendations
No official patch or fix is currently available for this vulnerability. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is released, administrators should consider disabling or restricting access to the WP Mail Logging plugin, especially limiting access to email logs to trusted users only. Additionally, review and minimize the installation of plugins or themes that may contain PHP Object Injection POP chains to reduce exploitation risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-02-13T15:25:20.955Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69a2918b32ffcdb8a20eaa4b
Added to database: 2/28/2026, 6:56:11 AM
Last enriched: 4/9/2026, 10:05:14 PM
Last updated: 4/14/2026, 5:52:39 PM
Views: 177
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.