CVE-2026-57423
Deferred Deferred - Pending Action

Cross-Site Scripting in Message Filter for Contact Form 7

Vulnerability report for CVE-2026-57423, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-13

Last updated on: 2026-07-13

Assigner: Patchstack

Description

Improper 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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-13
Last Modified
2026-07-13
Generated
2026-08-02
AI Q&A
2026-07-13
EPSS Evaluated
2026-08-01
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
kofi_mokome message_filter_for_contact_form_7 to 1.6.3.8 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a Cross-site Scripting (XSS) issue found in the Kofi Mokome Message Filter for Contact Form 7 plugin. It occurs because the plugin improperly neutralizes input during web page generation, allowing malicious scripts to be reflected back to users. This reflected XSS can be exploited when an attacker tricks a user into clicking a specially crafted link, causing the malicious script to run in the user's browser.

Detection Guidance

This vulnerability is a Reflected Cross-site Scripting (XSS) issue in the Kofi Mokome Message Filter for Contact Form 7 plugin. Detection typically involves checking for the presence of the vulnerable plugin version (<= 1.6.3.8) and testing for XSS payload reflection in web requests.

  • Check the installed version of the plugin: Verify if the plugin 'Message Filter for Contact Form 7' is installed on your WordPress site and confirm its version is <= 1.6.3.8. This can be done by logging into the WordPress admin dashboard, navigating to 'Plugins', and checking the version number.
  • Manual testing for XSS: Craft a URL or form input containing a simple XSS payload (e.g., <script>alert(1)</script>) and submit it via the Contact Form 7 interface. If the payload is reflected in the response without proper sanitization, the vulnerability may be present.
  • Use a web vulnerability scanner: Tools like OWASP ZAP, Burp Suite, or automated scanners (e.g., WPScan) can be used to scan for XSS vulnerabilities in web applications. Configure the scanner to target the Contact Form 7 endpoints and check for reflected input.
  • Review server logs: Inspect web server logs for unusual input patterns or repeated attempts to inject scripts, which may indicate exploitation attempts or testing for the vulnerability.
Impact Analysis

The vulnerability can lead to several impacts including unauthorized actions performed on behalf of the user, theft of sensitive information such as cookies or session tokens, and potential compromise of user accounts. Because the CVSS score is 7.1 with high impact on confidentiality, integrity, and availability, it indicates that attackers can cause significant harm by exploiting this reflected XSS vulnerability.

Compliance Impact

This vulnerability, a Reflected Cross-site Scripting (XSS) issue, can impact compliance with standards and regulations like GDPR and HIPAA due to its potential to expose sensitive data or allow unauthorized actions.

  • GDPR: Under GDPR, organizations must protect personal data from unauthorized access or disclosure. A Reflected XSS vulnerability could allow attackers to steal user session cookies, credentials, or other personal data entered into web forms, leading to a breach of confidentiality. This may result in non-compliance with GDPR's data protection requirements (e.g., Article 5 on data integrity and confidentiality) and could trigger reporting obligations under Article 33 (data breach notifications).
  • HIPAA: For organizations handling protected health information (PHI), HIPAA requires safeguards to ensure the confidentiality, integrity, and availability of PHI. An XSS vulnerability could enable attackers to intercept or manipulate PHI submitted via web forms, violating the HIPAA Security Rule (e.g., technical safeguards under 45 CFR Β§ 164.306). This could lead to unauthorized access to PHI, resulting in a reportable breach under the HIPAA Breach Notification Rule.

Additionally, the CVSS score of 7.1 (with impacts on confidentiality, integrity, and availability) indicates a moderate to high risk, which may draw scrutiny from regulators if the vulnerability is exploited and leads to a data breach.

Mitigation Strategies

To mitigate this vulnerability, follow these immediate steps:

  • Update the plugin: If an updated version of 'Message Filter for Contact Form 7' is available (version > 1.6.3.8), install it immediately to patch the vulnerability.
  • Disable the plugin: If no update is available, disable the plugin until a patch is released to eliminate the risk of exploitation.
  • Implement a Web Application Firewall (WAF): Configure a WAF to block XSS payloads and filter malicious input targeting the Contact Form 7 plugin.
  • Sanitize user input: If you have access to the plugin's code, manually sanitize user input by escaping or validating all output rendered in web pages to prevent XSS attacks.
  • Monitor for exploitation: Keep an eye on web server logs and user activity for signs of XSS exploitation attempts or unusual behavior.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-57423. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart