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

> Unauthenticated attackers can inject PHP objects via email logs, potentially leading to code execution or data theft if a POP chain exists.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-675c-q49r-3647

## What is CVE-2026-2471?

CVE-2026-2471 is a high-severity unsafe deserialization vulnerability in smub WP Mail Logging, published on 28 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-2471?


## How do I fix CVE-2026-2471?

No fix has been published for CVE-2026-2471 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2471 being exploited?

There is no known exploitation of CVE-2026-2471 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2471 and fix it if it is affected.

What it is: CVE-2026-2471 is a high-severity unsafe deserialization vulnerability in smub WP Mail Logging, published on 28 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-2471 in the wild and no public exploit code.

Affected product: smub WP Mail Logging. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2471/ (Markdown: https://insights.sbomify.com/CVE-2026-2471/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2471
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2471
- OSV: https://osv.dev/vulnerability/CVE-2026-2471

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2471/
Summaries are generated and may contain mistakes; the official description above is the record.