dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-58604

HIGH · 7.6 CVSS v3.1 Published 2025-09-03
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.5.

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 allows attackers to inject malicious SQL commands through unsanitized user input. This occurs in the mail-mint component where special characters in input are not properly neutralized before being used in database queries.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries, implement proper input validation and sanitization on all user-supplied data before using it in database operations.

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 /wp-content/plugins directory for a mail-mint folder
    Affected if Mail Mint plugin is present in the WordPress installation
  2. Determine installed Mail Mint version
    In WordPress admin, go to Plugins > Installed Plugins, find Mail Mint, and note the version number displayed, or check the version in the plugin's main PHP file header
    Affected if The installed version matches any affected version range (compare your version to official WordPress plugin repository release notes for this CVE)
  3. Identify if mail-mint component is active
    Check WordPress admin for any active Mail Mint forms, campaigns, or mailing lists that use the mail-mint functionality
    Affected if Any Mail Mint features (forms, campaigns, lists) are actively configured and in use
  4. Review database query logs for suspicious patterns
    Enable WordPress debug logging or review database logs for queries containing UNION, SELECT, or unusual character sequences in parameters passed to mail-mint endpoints
    Affected if Unusual SQL syntax or unexpected SQL commands appear in database query logs
  5. Check for unauthorized database changes
    Review database tables (especially those prefix with mint_ or used by Mail Mint) for unexpected new tables, modified records, or unfamiliar data entries
    Affected if Unknown tables, modified user data, or suspicious records exist in the database

A user is affected if Mail Mint plugin is installed, the installed version is within the affected range, and the mail-mint component is actively processing user input.

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

Replace dynamic SQL queries with prepared statements/parameterized queries, implement proper input validation and sanitization on all user-supplied data before using it in database operations.

Recommended fix Moderate confidence

Mail Mint version > 1.18.5 (contact vendor for exact fixed release)

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the Mail Mint plugin in the plugin list
  4. 4. Check if an update is available for Mail Mint
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. After updating, verify the plugin is functioning correctly and test critical workflows
  7. 7. Monitor plugin vendor channels for any additional security advisories
Caveat Review plugin changelog for any breaking changes between your current version and the new version before updating

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58604 — 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-58604 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