Answer in brief
CVE-2026-12918 records a Medium severity (CVSS 4.9) vulnerability in Mail Mint <= 1.24.1 - Authenticated (Administrator+) SQL Injection via 'recipients' Parameter. The current sources do not mark it as known exploited. The current feed maps getwpfunnels/Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emails (generic), getwpfunnels/Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emails (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps getwpfunnels/Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emails (generic), getwpfunnels/Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emails (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| getwpfunnels/Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emailsgeneric | 0 | Not reported |
| getwpfunnels/Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emailsgeneric | >=0 <=1.24.1 | Not reported |
Published upstream
Jul 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 10, 2026
The Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emails plugin for WordPress is vulnerable to generic SQL Injection via the 'recipients' parameter in all versions up to, and including, 1.24.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is a second-order SQL injection: the malicious payload is first stored unsanitized via a POST request to /mrm/v1/campaigns/ (bypassing filter_recipients() validation because an int-cast of a string like '1) OR ...' evaluates to a real numeric ID), and is then triggered by a subsequent GET request to /mrm/v1/campaigns/{id} that deserializes the recipients and passes the raw id string through array_column() into the vulnerable query.
Quoted source text, attributed separately from HOL analysis.