CVE-2026-57423
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Kofi Mokome Message Filter for Contact Form 7 cf7-message-filter allows Reflected XSS.This issue affects Message Filter for Contact Form 7: from n/a through <= 1.6.3.8.
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 confidenceReflected XSS vulnerability in the Message Filter for Contact Form 7 plugin (cf7-message-filter) versions through 1.6.3.8. User-supplied input is not properly sanitized before being reflected back in web pages, allowing attackers to inject malicious JavaScript code via crafted requests.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedIn WordPress admin, navigate to Plugins > Installed Plugins and look for 'Message Filter for Contact Form 7' or 'cf7-message-filter' in the list. Note whether it is installed and activated.Affected if The plugin is present and active in the WordPress installation.
-
Identify installed versionIn the Plugins list, locate the cf7-message-filter entry and read the version number displayed beneath the plugin name. Compare this version to the affected range (any version through 1.6.3.8).Affected if The installed version is 1.6.3.8 or lower.
-
Verify plugin handles form submissionsExamine whether the plugin is configured to process Contact Form 7 submissions. This can be done by checking the plugin settings page in WordPress admin under Contact > Message Filter, or by reviewing if CF7 forms are using any filtering features provided by this plugin.Affected if The plugin is actively processing Contact Form 7 form submissions.
-
Inspect for unsanitized reflection pointsReview plugin source code files (typically in wp-content/plugins/cf7-message-filter/) for any instances where user-supplied input from form submissions is output without using WordPress sanitization functions like sanitize_text_field(), esc_html(), or esc_attr(). Look for direct echo or print statements containing $_POST, $_GET, or CF7 submission data.Affected if Code is found that reflects user input without proper sanitization or encoding.
A user is affected if the cf7-message-filter plugin is installed with version 1.6.3.8 or lower and is actively processing Contact Form 7 form submissions.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate to the latest version of the plugin when a patch is released, or implement proper input sanitization using WordPress sanitization functions (such as sanitize_text_field()) and output encoding (esc_html(), esc_attr()) for all user inputs before rendering.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57423 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57423 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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