CVE-2026-19800 Mail Mint <= 1.31.0 - Authenticated (Custom+) SQL Injection via 'status' Parameter
Authenticated administrators can exploit SQL injection in the status parameter to extract sensitive database information from the Mail Mint plugin.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-19800?
CVE-2026-19800 is a medium-severity SQL injection vulnerability in getwpfunnels Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emails, published on 9 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
The Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emails plugin for WordPress is vulnerable to SQL Injection via the 'status' parameter in all versions up to, and including, 1.31.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. The $wpdb->prepare() call does not protect against this injection because the attacker-controlled $contact_filter_query fragment is concatenated into the SQL format string before prepare() executes — prepare() only processes %s/%d placeholders and cannot sanitize content already embedded in the format string. REST API JSON bodies are parsed from php://input and bypass WordPress's wp_magic_quotes(), meaning double-quote characters in status array values reach the SQL sink unescaped. 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. The required 'mint_read_contacts' capability is a plugin-specific capability not assigned to any default WordPress role; it must be explicitly granted by an administrator, making this effectively an Administrator+ vulnerability.
Weakness: CWE-89
Which versions are affected by CVE-2026-19800?
How do I fix CVE-2026-19800?
No fix has been published for CVE-2026-19800 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-19800 being exploited?
There is no known exploitation of CVE-2026-19800 in the wild and no public exploit code.
Sources
Also known as GHSA-7rj2-4m28-2wfr.