dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-59570

HIGH · 7.6 CVSS v3.1 Published 2025-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WPFunnels Mail Mint mail-mint allows SQL Injection.This issue affects Mail Mint: from n/a through <= 1.18.6.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in the Mail Mint WordPress plugin (WPFunnels) allows attackers to inject malicious SQL commands through unsanitized user input. The flaw exists in the mail-mint component and affects all versions through 1.18.6. Successful exploitation could enable unauthorized data access, modification, or deletion from the database.

MitigationUpdate Mail Mint to the latest version once a security patch is released. If no patch is available, implement parameterized queries or input sanitization at the application layer to prevent SQL injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Mail Mint plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Mail Mint' or check the file /wp-content/plugins/mail-mint/ exists
    Affected if Mail Mint plugin is not installed or not present in the plugins directory
  2. Check installed Mail Mint version
    Navigate to Plugins > Installed Plugins > Mail Mint and read the version number displayed, or inspect /wp-content/plugins/mail-mint/mail-mint.php and look for 'Version:' in the plugin header
    Affected if Version is 1.18.6 or earlier (all versions through 1.18.6 are affected)
  3. Confirm mail-mint component is active
    Check WordPress admin for Mail Mint functionality accessible via dashboard menu, or inspect /wp-content/plugins/mail-mint/ for active module files related to the mint component
    Affected if The mail-mint component is enabled and accessible in the WordPress environment
  4. Identify vulnerable SQL input point
    Review server access logs for POST/GET requests to Mail Mint endpoints containing unsanitized user parameters (e.g., parameters passed to database queries without prepare() or escaping), or inspect plugin source code in /wp-content/plugins/mail-mint/ for direct SQL queries using $wpdb->prepare with user-supplied input
    Affected if User-supplied input is being used in SQL queries without proper parameterization or sanitization

Your environment is affected if Mail Mint plugin versions 1.18.6 or earlier are installed with the mail-mint component active and handling user input that reaches unsanitized SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Mail Mint to the latest version once a security patch is released. If no patch is available, implement parameterized queries or input sanitization at the application layer to prevent SQL injection.

Recommended fix Moderate confidence

Latest version of Mail Mint (greater than 1.18.6) - check WordPress plugin repository or vendor for the specific fixed release

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Mail Mint plugin in the list
  4. 4. If an update is available, click 'Update Now' to update Mail Mint to the latest version
  5. 5. After updating, verify the plugin version in Plugins > Installed Plugins to confirm the update was applied
  6. 6. Test critical functionality (especially any forms or email capture features) to ensure the plugin continues to work correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59570 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59570 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data