mediumCVE-2026-14342

Mail Mint WordPress Plugin Time-Based SQL Injection Vulnerability

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.

ProductMail Mint
CVSS4.9
EPSS0.00266
UpdatedJuly 10, 2026

Quick answer

Mail Mint should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • Mail Mint up to and including 1.24.2

Fixed versions

  • Apply the latest vendor-supported patched version.

How to fix it

Mail Mint is affected by CVE-2026-14342. Vulnerable versions up to 1.24.2 allow SQL injection: administrator-level attackers can use the contact_ids parameter for time-based SQL injection. Patch quickly, review database access logs, and reduce access to the affected admin functions.

  1. Inventory WordPress sites using Mail Mint.
  2. Update Mail Mint beyond 1.24.2 when a vendor-fixed release is available.
  3. Restrict the affected plugin admin functions to trusted administrators until patched.
  4. Back up the WordPress database before applying remediation.
  5. Review web and database logs for SQL metacharacters, time-delay probes, and suspicious query errors.
  6. Rotate database credentials if unauthorized data extraction is suspected.
  7. Clear object and page caches after the plugin is updated.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm Mail Mint is no longer running version 1.24.2 or older.
  • Run safe SQL injection regression tests in staging and confirm payloads are parameterized or rejected.
  • Confirm database errors are not exposed in HTTP responses.
  • Review logs after patching for blocked SQLi attempts.
  • Run a Fixnx scan and verify public WordPress exposure after remediation.

Related categories

Trusted references

FAQ

What is affected by CVE-2026-14342?

Mail Mint versions listed as affected should be reviewed: Mail Mint up to and including 1.24.2.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

Why can this risk appear in multiple categories?

A vulnerability can belong to more than one platform or ecosystem. Fixnx keeps one canonical risk page while also listing it in every relevant category.