Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-84753 – Unauthenticated PHP Object Injection – Mail Mint WordPress Plugin ≤ 1.31.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-84753 is a critical, unauthenticated PHP Object Injection (Deserialization of Untrusted Data) vulnerability affecting the Mail Mint WordPress plugin, developed by WPFunnels. The flaw affects all versions up to and including 1.31.0 and carries a CVSS v3.1 base score of 9.8 (Critical), as it can be triggered remotely without authentication or user interaction.

Technical details

  • Root cause: the plugin passes attacker-controlled input to PHP’s unserialize() function without adequate validation or sanitization, classified as CWE-502 (Deserialization of Untrusted Data).
  • Trigger conditions: an unauthenticated attacker submits crafted serialized data through a plugin-exposed action, such as a frontend form submission, which is then deserialized by the plugin.
  • Attack vector: Network (AV:N), Attack Complexity: Low (AC:L), Privileges Required: None (PR:N), User Interaction: None (UI:N).
  • Impact: successful exploitation can result in PHP Object Injection; depending on other classes and gadget chains present on the target site, this can lead to arbitrary file operations, code execution, or complete compromise of confidentiality, integrity, and availability.

Affected software

  • Mail Mint (WordPress plugin) by WPFunnels — all versions up to and including 1.31.0
  • Fixed in version 1.31.1

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Update the Mail Mint plugin to version 1.31.1 or later, where the PHP Object Injection issue on unauthenticated form submission has been fixed.
  • If immediate patching is not possible: restrict or disable public-facing Mail Mint form submission endpoints, deploy a web application firewall rule to block serialized-object payloads (e.g., strings containing PHP serialization markers such as O:, a:, s:) in form input, and monitor logs for anomalous POST requests to plugin endpoints.
  • Following patching, review site integrity for signs of prior exploitation, including unexpected files, admin accounts, or scheduled tasks.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /wp-content/plugins/mail-mint/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge