Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Mon, 02 Mar 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 02 Mar 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Smub
Smub wp Mail Logging Wordpress Wordpress wordpress |
|
| Vendors & Products |
Smub
Smub wp Mail Logging Wordpress Wordpress wordpress |
Sat, 28 Feb 2026 06:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | WP Mail Logging <= 1.15.0 - Unauthenticated PHP Object Injection via Email Log Message Field | |
| Weaknesses | CWE-502 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Wordfence
Published:
Updated: 2026-03-02T19:41:20.206Z
Reserved: 2026-02-13T15:25:20.955Z
Link: CVE-2026-2471
Updated: 2026-03-02T19:41:15.855Z
Status : Awaiting Analysis
Published: 2026-02-28T07:15:57.677
Modified: 2026-03-02T20:30:10.923
Link: CVE-2026-2471
No data.
OpenCVE Enrichment
Updated: 2026-03-02T12:04:26Z