dbcve.org
Message Filter For Contact Form 7WordPress extension · Kofimokome

CVE-2025-46252

HIGH · 7.2 CVSS v3.1 Published 2025-04-22
Fix available
A fix is available. Upgrade to 1.6.3.3 or later.
See remediation →
78/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 Kofi Mokome Message Filter for Contact Form 7 cf7-message-filter allows SQL Injection.This issue affects Message Filter for Contact Form 7: from n/a through <= 1.6.3.2.

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

A SQL injection vulnerability exists in the Message Filter for Contact Form 7 plugin (cf7-message-filter) versions up to 1.6.3.2 due to improper neutralization of special elements in SQL commands. This allows authenticated attackers to inject malicious SQL queries, potentially enabling data exfiltration or database compromise.

MitigationUpdate the plugin to the latest version once available. If no patch exists, implement a WAF rule or temporarily disable the plugin until a fix is released.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Message Filter For Contact Form 7WordPress extension
Affected:< 1.6.3.3

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'cf7-message-filter' or search for 'message-filter-for-contact-form-7' or similar. Also check in WordPress admin under Plugins > Installed Plugins.
    Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in WordPress admin plugin list.
  2. Identify installed version
    Open the main plugin file (usually cf7-message-filter.php or similar in the plugin folder) and locate the 'Version' header in the plugin comments. Alternatively, check the WordPress plugin admin page which displays versions.
    Affected if The version number found is less than 1.6.3.3 (for example, 1.6.3.2, 1.6.3.1, 1.6.3, 1.6.2, etc.).
  3. Verify plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and check if the Message Filter for Contact Form 7 plugin has an 'Active' status. Alternatively, query the wp_options table for the active_plugins option.
    Affected if The plugin shows as 'Active' in WordPress admin or appears in the active_plugins option in the database.
  4. Assess authentication exposure
    Determine if any user accounts exist on the WordPress site that could be leveraged to exploit this vulnerability. Check if user registration is enabled or if there are any user accounts beyond the administrator (contributor, author, editor, subscriber roles).
    Affected if The site has at least one user account beyond the primary administrator, or user registration is enabled, allowing an authenticated attacker to access the vulnerable code path.

A user is affected if the Message Filter for Contact Form 7 plugin is installed, active, and running a version lower than 1.6.3.3, with at least one authenticated user account present on the site.

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
Upgrade available Upgrade to 1.6.3.3 or later
Fixed in 1.6.3.3
Interim mitigation

Update the plugin to the latest version once available. If no patch exists, implement a WAF rule or temporarily disable the plugin until a fix is released.

Recommended fix High confidence

1.6.3.3

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard > Plugins
  3. 3. Locate 'Message Filter For Contact Form 7' in the installed plugins list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.6.3.3 or later
  5. 5. Alternatively, download the latest version from the WordPress plugin repository or the vendor
  6. 6. After updating, verify the plugin version shows 1.6.3.3 or higher
  7. 7. Test the contact form functionality to ensure the plugin is working correctly after the update

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

Fix this in Message Filter For Contact Form 7 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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