LiveActive security incident?Get immediate response
CVE Record

CVE-2026-10196: Mail Mint <= 1.31.0 - Unauthenticated PHP Object Injection in Arbitrary Form Fields

The Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emails plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.31.0 via deserialization of untrusted input in the 'handle_form_submission' function. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to execute code on the server. The vulnerability was partially patched in version 1.23.1.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

An internet attacker could submit malicious data through Mail Mint forms and potentially take control of the WordPress server without logging in. Successful exploitation could expose customer data, alter website content, disrupt service, or enable further compromise. The supplied record says versions through 1.31.0 are affected and that an earlier fix was incomplete.

Executive priority

Treat this as an emergency exposure check for internet-facing WordPress systems. Prioritize identifying affected installations, limiting public access, and applying a vendor-confirmed complete remediation. Because code execution could compromise the entire server, exposed systems warrant investigation even though active exploitation is not established by the supplied evidence.

Technical view

Mail Mint through 1.31.0 deserializes untrusted input in handle_form_submission, enabling unauthenticated PHP object injection through arbitrary form fields. The reported presence of a suitable POP chain can turn object injection into server-side code execution. The CVSS 3.1 score is 9.8, reflecting network access, low complexity, and no required privileges or user interaction.

Likely exposure

WordPress sites running Mail Mint 1.31.0 or earlier should be considered potentially exposed, particularly when form submission functionality is reachable by unauthenticated visitors. The bundle does not establish whether every installation exposes a usable form or POP chain configuration, so site-specific validation remains necessary.

Exploitation context

The supplied sources describe unauthenticated remote code execution potential, but provide no evidence of active exploitation. The CVE is not listed as KEV in the bundle. Exploit attempts may be difficult to distinguish from ordinary form traffic without application, web-server, and host-level monitoring.

Researcher notes

The source bundle contains inconsistent affected-product metadata: its narrative says all versions through 1.31.0, while the structured affected entry lists version “0” with a default unaffected status. The narrative also says 1.23.1 was only partially patched but names no fully fixed release. These gaps reduce certainty about precise version boundaries and remediation status.

Mitigation direction

  • Inventory WordPress sites and identify every installed Mail Mint version.
  • Check current vendor guidance for a release confirmed to fully remediate CVE-2026-10196.
  • Disable Mail Mint or restrict affected form functionality until a complete vendor-confirmed fix is applied.
  • Back up affected systems before updating, then apply the confirmed remediation promptly.
  • Increase monitoring for anomalous form submissions and unexpected server-side changes.

Validation and detection

  • Confirm whether each site runs Mail Mint 1.31.0 or earlier.
  • Determine whether Mail Mint forms accept submissions from unauthenticated users.
  • Verify the deployed release is vendor-confirmed as fully fixed, not merely the partial 1.23.1 patch.
  • Review web, WordPress, and host logs for unusual form activity or unexpected changes.
  • After remediation, confirm forms operate normally and the vulnerable version is absent.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-10196 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
1ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Wordfence

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-10196Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. Source timelineWordfence

    Vendor Notified

  3. Source timelineWordfence

    Disclosed

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
getwpfunnelsMail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emails0unaffected
Weakness

CWE details

CWE-502

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs