CVE-2026-111106 json
Mail Mint <= 1.31.4 - Authenticated (Custom+) SQL Injection via 'filters' Parameter
published 24d ago modified 24d ago also EUVD-2026-102640
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-111106 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 24d ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- getwpfunnels Mail Mint – Email Marketing, Automation & WooCommerce Emails with AI Assistance
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/7c492357-3293-49cf-9e4a-3e144b58b6f7?source=cve
- plugins.trac.wordpress.org /browser/mail-mint/tags/1.31.4/app/Internal/Admin/Segmentation/SegmentFilterService.php#L797
- plugins.trac.wordpress.org /browser/mail-mint/tags/1.31.4/app/Internal/Admin/Segmentation/SegmentFilterService.php#L500
- plugins.trac.wordpress.org /browser/mail-mint/tags/1.31.4/app/Internal/Admin/Segmentation/SegmentFilterService.php#L100
- plugins.trac.wordpress.org /browser/mail-mint/tags/1.31.4/app/API/Controllers/Admin/SegmentController.php#L41
- plugins.trac.wordpress.org /browser/mail-mint/tags/1.31.4/app/API/Routes/Admin/SegmentRoute.php#L55
- plugins.trac.wordpress.org /browser/mail-mint/tags/1.31.4/app/Internal/Admin/Segmentation/SegmentFilterService.php#L297
- plugins.trac.wordpress.org /changeset/3743638/mail-mint/trunk/app/Internal/Admin/Segmentation/SegmentFilterService.php
Sources
- CVE List CVE-2026-111106
- NVD CVE-2026-111106
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.