Security readout for executives and security teams
Plain-English summary
Mail Mint versions through 1.31.0 reportedly allow an unauthenticated internet attacker to inject PHP objects. Successful exploitation could compromise website data, integrity, or availability. The supplied sources do not document confirmed attacks or a specific fixed version.
Executive priority
Treat this as an urgent exposure-assessment and remediation item for public WordPress sites. Prioritize systems processing sensitive data or business-critical communications. Do not claim compromise solely from plugin presence, but investigate exposed installations because authentication is reportedly unnecessary and potential impact is severe.
Technical view
CVE-2026-84753 is classified as CWE-502, insecure deserialization, with CVSS 3.1 score 9.8. The supplied description identifies unauthenticated PHP object injection in Mail Mint through 1.31.0. Exact vulnerable endpoints, prerequisites, gadget chains, and resulting code-execution conditions are not provided.
Likely exposure
Internet-facing WordPress sites with Mail Mint enabled at version 1.31.0 or earlier are the likely exposure population. Actual exploitability may depend on site-specific PHP classes or plugins. The bundle’s structured affected record says versions are unavailable and defaults to unaffected, conflicting with its title and description.
Exploitation context
The CVSS vector indicates remote, low-complexity exploitation requiring neither authentication nor user interaction, with potentially high confidentiality, integrity, and availability impact. KEV is false, and the supplied sources provide no evidence of active exploitation or public exploit availability.
Researcher notes
Available evidence establishes the vulnerability class, claimed affected ceiling, and severity, but omits the vulnerable endpoint, data flow, gadget requirements, proof of concept, and fixed version. The affected-version metadata conflicts with the narrative. Validate against updated vendor, CVE, and Patchstack records before making definitive scope claims.
Mitigation direction
- Identify every WordPress site running Mail Mint and record its installed version.
- Check WPFunnels and Patchstack guidance for a confirmed fixed release.
- Upgrade promptly when a vendor-confirmed fixed version is available.
- If no fix is available, disable or remove Mail Mint until vendor guidance is published.
- Back up affected sites before remediation and restrict administrative access.
Validation and detection
- Confirm Mail Mint is absent, disabled, or newer than the vendor-confirmed affected range.
- Verify the installed plugin files and version against a trusted distribution.
- Review web, application, and security logs for anomalous unauthenticated Mail Mint requests.
- Check WordPress for unexpected administrators, modified files, injected content, or configuration changes.
- Monitor vendor and CVE records for corrected affected-version and remediation details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2026-84753 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/plugin/mail-mint/vulnerability/wordpress-mail-mint-plugin-1-31-0-php-object-injection-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.