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

Back
New CVE Detected

CVE-2026-10196 – Unauthenticated PHP Object Injection (RCE) – 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-10196 is a critical PHP Object Injection vulnerability (CWE-502) in the Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emails WordPress plugin, caused by deserialization of untrusted input in the handle_form_submission function. The flaw affects all plugin versions up to and including 1.31.0 and allows unauthenticated attackers to inject arbitrary PHP objects; combined with an available POP (Property-Oriented Programming) chain in the plugin, this can lead to remote code execution on the underlying server. The issue carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: The plugin’s handle_form_submission function deserializes attacker-controlled input without proper validation, enabling PHP Object Injection.
  • Trigger conditions: An attacker submits a crafted form request to a WordPress site running the vulnerable Mail Mint plugin; no authentication is required to reach the vulnerable code path.
  • Attack vector: Network — exploitable remotely over HTTP with no privileges and no user interaction required.
  • Impact: If a usable POP chain exists in the plugin or another installed component, successful exploitation can result in remote code execution, along with high impact to confidentiality, integrity, and availability of the affected site.
  • A partial patch was applied in version 1.23.1, but the underlying deserialization issue was reported to persist through version 1.31.0.

Affected software

  • Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emails (WordPress plugin by getwpfunnels): all versions up to and including 1.31.0.

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 Mail Mint to the latest version available from the WordPress plugin repository beyond 1.31.0; confirm with the vendor that a complete fix for the deserialization flaw has been released, since the 1.23.1 patch was only partial.
  • If no confirmed patch is available: Restrict or disable public access to the Mail Mint form submission endpoint, deploy a web application firewall rule to block requests containing serialized PHP object payloads targeting handle_form_submission, and monitor logs for anomalous POST requests to the plugin’s endpoints.
  • Review the site for indicators of compromise (unexpected files, admin accounts, or scheduled tasks) if the plugin was exposed prior to patching.

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