Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with mint_read_contacts capability
-
DeliverySend crafted 'filters' value to segments/contacts endpoint
-
ExploitBreak out of numeric WHERE context (SQLi)
-
ExecutionAppend UNION/subquery to database query
-
ImpactExtract sensitive data from WordPress DB
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account holding the plugin-specific 'mint_read_contacts' capability, which is granted only to Administrators by default but can be delegated to lower-privileged roles through Mail Mint's built-in role manager. Exploitation is performed against the /wp-json/mrm/v1/segments/contacts REST endpoint by supplying a malicious filter 'value' that lands in an unquoted numeric SQL context not covered by $wpdb->prepare(). The principal limiting factor is this capability requirement: in a default configuration the attacker must already be an Administrator (making the practical impact low), whereas the realistic risk arises specifically on sites that have reassigned 'mint_read_contacts' to lower roles. No special user interaction is needed, and the plugin must be at version 1.31.4 or earlier. |
| Impact | This is a genuine but moderate-priority issue rather than a top-tier emergency. The CVSS 6.5 (Medium) vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N is internally consistent with the description: network-reachable REST endpoint, low attack complexity, and a confidentiality-only impact (data extraction via SQLi) with no integrity or availability effect. The key risk-limiting signal is PR:L - exploitation requires an authenticated account holding the custom 'mint_read_contacts' capability, which by default is only granted to Administrators. The real-world risk therefore hinges on whether a site operator has used the plugin's role manager to extend that capability to lower-privileged roles; in default deployments the attacker would already need admin-equivalent access, sharply reducing practical severity, whereas in reconfigured deployments a low-privileged user could read arbitrary database contents. No EPSS score, KEV listing, or POC was provided in the input, so there is no evidence of active exploitation or public exploit code - exploitation status is therefore 'no public exploit identified at time of analysis.' The vendor-assigned Medium rating looks appropriate and is not an inflated high-CVSS-but-low-risk case. |
| Exploit ScenarioDerived | An attacker who holds (or has been granted) the 'mint_read_contacts' capability sends a crafted request to the /wp-json/mrm/v1/segments/contacts REST endpoint with a malicious 'filters' value. Because the value is string-interpolated into an unquoted numeric context in SegmentFilterService::get_meta_join_query() outside the protection of $wpdb->prepare(), the attacker appends a UNION/sub-query to exfiltrate data such as password hashes or other sensitive table contents. No public exploit code was identified at time of analysis, but the vulnerable source line is publicly disclosed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
SQL injection in the Mail Mint plugin for WordPress (versions up to and including 1.31.4) allows an authenticated attacker with the plugin-specific 'mint_read_contacts' capability to read sensitive database contents through the /wp-json/mrm/v1/segments/contacts REST endpoint. The issue is a genuine but moderate-priority SQL injection rather than a top-tier emergency because the capability is granted only to Administrators by default, although sites that have delegated it to lower-privileged roles via Mail Mint's role manager face greater risk. No public exploit identified at time of analysis; no KEV or EPSS data was provided.
RemediationAI
Upstream fix available (changeset/commit); released patched version not independently confirmed. Update Mail Mint beyond 1.31.4 as soon as a tagged patched release is published, and review the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/7c492357-3293-49cf-9e4a-3e144b58b6f7?source=cve plus the upstream changeset at https://plugins.trac.wordpress.org/changeset/3743638/mail-mint/trunk/app/Internal/Admin/Segmentation/SegmentFilterService.php for fix confirmation. If an immediate update is not possible, the most targeted compensating control is to ensure that only trusted Administrator accounts hold the 'mint_read_contacts' capability and to remove it from all lower-privileged roles in Mail Mint's role manager; the trade-off is that legitimate non-Administrator users who rely on segment/contact management may lose access. For sites that do not need Mail Mint, temporarily deactivate the plugin, which eliminates the vulnerable REST endpoint but disables all Mail Mint email marketing and automation features. Blocking or filtering access to /wp-json/mrm/v1/segments/contacts can also reduce exposure, but it may break segment-contact operations and is not a complete fix; a WAF rule targeting suspicious SQL syntax in the 'filters' parameter may add temporary protection but can be bypassed.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a CWE-89 SQL injection in Mail Mint's SegmentFilterService::get_meta_join_query() at line 797 in version 1.31.4. User-supplied filter data reaches this method through the /wp-json/mrm/v1/segments/contacts REST endpoint, which is handled by SegmentController and registered in SegmentRoute. The filter 'value' is appended to a SQL WHERE fragment in a numeric and unquoted context, and the surrounding $wpdb->prepare() calls do not cover the injected value, so an attacker can break out of the intended numeric expression and append SQL. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N confirms a network-reachable, authenticated, low-privileged, no-interaction, confidentiality-only impact. The plugin CPE cpe:2.3:a:getwpfunnels:mail_mint_-_email_marketing,_automation_&_woocommerce_emails_with_ai_assistance:*:*:*:*:*:*:*:* identifies the affected WordPress plugin, and the condition applies to versions up to and including 1.31.4.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Network REST endpoint (AV:N) with no special complexity (AC:L); requires the mint_read_contacts capability so PR:L; SQLi enables full data read (C:H) with no write/DoS, so I:N/A:N.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Mail Mint plugin for WordPress is vulnerable to SQL Injection via the 'filters' parameter of the /wp-json/mrm/v1/segments/contacts REST endpoint in versions up to, and including, 1.31.4 This is due to insufficient escaping on the user supplied filter 'value' before it is appended to a SQL query in SegmentFilterService::get_meta_join_query() at line 797, where the value is string-interpolated into the WHERE fragment in a numeric (unquoted) context and the surrounding $wpdb->prepare() calls do not cover the injected value. This makes it possible for authenticated attackers, with the custom 'mint_read_contacts' capability (granted to Administrators by default, and configurable to lower roles via the plugin's role manager), to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-102640
GHSA-x22g-vhr9-fpv2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB