MEDIUM 4.9

CVE-2026-14342: SQL Injection in Mail Mint WordPress Plugin (v1.24.2 and Earlier)

The Mail Mint WordPress plugin, used for email marketing and WooCommerce integration, contains a SQL injection vulnerability affecting all versions up to 1.24.2. An authenticated administrator can manipulate the 'contact_ids' parameter to inject malicious SQL commands and extract sensitive data from the WordPress database. While access requires administrator-level privileges, the vulnerability allows unauthorized data exfiltration once those credentials are compromised or misused.

Source data · NVD / CISA · public domain

CVSS
3.1 · 4.9 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Weaknesses (CWE)
CWE-89
Affected products
0 configuration(s)
Published / Modified
2026-07-09 / 2026-07-09

NVD description (verbatim)

The Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emails plugin for WordPress is vulnerable to time-based SQL Injection via the 'contact_ids' parameter in all versions up to, and including, 1.24.2 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.

5 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-14342 is a time-based SQL injection flaw in the Mail Mint plugin's handling of the 'contact_ids' parameter. The vulnerability stems from insufficient input escaping and lack of parameterized query preparation. An attacker with administrator or higher privileges can craft malicious SQL to append additional queries to existing database statements, enabling data extraction through inference techniques. The attack surface is limited by authentication requirements but represents a privilege abuse risk when admin accounts are compromised.

Business impact

Compromise of a WordPress administrator account could lead to unauthorized extraction of sensitive business data from the site's database, including customer information, email lists, transaction records, and other confidential details stored by the Mail Mint plugin or other installed plugins. This poses direct risks to customer privacy, regulatory compliance (GDPR, CCPA), and business reputation. Data exfiltration is particularly concerning for e-commerce sites using WooCommerce with customer payment and personal information at risk.

Affected systems

WordPress installations running the Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emails plugin in version 1.24.2 and earlier are affected. The vulnerability requires an authenticated user with administrator-level access or higher to exploit, meaning it primarily affects sites where admin accounts have been compromised, insiders pose a threat, or accounts are carelessly shared.

Exploitability

Exploitation requires valid WordPress administrator credentials, which significantly limits attack surface in well-secured environments. However, once those credentials are obtained through credential theft, phishing, or insider threats, exploitation is straightforward and requires no user interaction. The vulnerability is reliably exploitable through time-based inference techniques, making automated detection by skilled attackers feasible. The CVSS score of 4.9 reflects the requirement for high-privilege access but acknowledges the certainty of successful data extraction.

Remediation

Update the Mail Mint plugin to a version patched after 1.24.2 as soon as vendor patches become available. In parallel, enforce strict WordPress user access controls by limiting administrator role assignment, implementing strong password policies, enabling multi-factor authentication for admin accounts, and conducting regular access reviews. Monitor database query logs for suspicious SQL patterns and restrict admin panel access by IP address where feasible.

Patch guidance

Verify the vendor's official advisory for the specific patched version of Mail Mint. Test patches in a staging environment before deployment to production WordPress sites. Given the plugin's integration with WooCommerce and email systems, ensure compatibility with your site's current configuration. Apply the patch promptly to all affected installations, prioritizing sites handling sensitive customer or financial data.

Detection guidance

Monitor database logs for unusual SQL queries or syntax errors in queries containing the 'contact_ids' parameter. Track WordPress admin login events and administrative actions within the Mail Mint plugin interface. Deploy Web Application Firewall (WAF) rules to flag SQL injection attempts targeting common parameters. Use WordPress security plugins with database activity logging and anomaly detection capabilities. Audit plugin code and database queries if you maintain custom integrations with Mail Mint.

Why prioritize this

While the CVSS score of 4.9 reflects medium severity, the vulnerability should be prioritized based on your organization's data sensitivity and WordPress exposure. Sites handling customer payment data, personal information, or regulated content warrant immediate patching. The vulnerability's reliance on admin access provides a natural prioritization lens: assess the security posture of your WordPress administrator accounts and the likelihood of compromise in your threat environment.

Risk score, explained

The CVSS 3.1 score of 4.9 (MEDIUM) factors in: (1) Network accessibility without special conditions (AV:N/AC:L), (2) High privilege requirement reducing likelihood of exploitation (PR:H), (3) No user interaction needed (UI:N), (4) Isolated impact scope (S:U), and (5) Confidentiality impact through data extraction (C:H) with no integrity or availability impact (I:N/A:N). The high confidentiality impact is offset by the authentication barrier, yielding a moderate overall rating.

Frequently asked questions

Can this vulnerability be exploited by regular WordPress users or subscribers?

No. The vulnerability requires WordPress administrator-level access or higher, making regular users, contributors, and editors unable to exploit it. The risk is primarily insider threats, credential compromise of admin accounts, and privilege escalation attacks that first compromise a lower-privileged account.

What data can be extracted using this SQL injection?

An attacker can extract any data stored in the WordPress database accessible to the database user's privileges, including user credentials, customer information, email lists, WooCommerce transaction records, and any sensitive information stored by other plugins. The scope depends on what data your site stores and the database user's permission level.

Is this vulnerability actively exploited in the wild?

As of the publication date, CVE-2026-14342 is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, indicating no confirmed public exploits at this time. However, the simplicity of SQL injection attacks suggests you should patch proactively rather than wait for evidence of active exploitation.

Can a WAF or security plugin prevent exploitation without patching?

A WAF or security plugin can detect and block obvious SQL injection attempts, but a determined attacker with admin credentials can craft sophisticated time-based queries that evade simple pattern matching. These defenses are helpful layers but should not replace patching. Proper remediation requires updating the plugin to a fixed version.

This analysis is based on publicly disclosed information current as of the publication date. Patch version numbers, vendor advisory details, and exploit status are subject to change; verify against the official Mail Mint plugin release notes and WordPress plugin repository before deploying patches. This assessment does not constitute professional security advice for your specific environment—consult your security team and conduct testing in non-production systems before applying mitigations. The absence of confirmed public exploits does not guarantee the vulnerability is not being exploited privately; treat it as a material risk requiring prompt remediation. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).