CVE-2025-12718

Quick Contact Form <= 8.2.6 - Unauthenticated Open Mail Relay

Strategic Overview

Status
Patched in 8.2.7
Affected Plugin
Quick Contact Form
Affected Version
<= 8.2.6
CVSS
5.8Medium
Weakness type
CWE-20 · Improper Input Validation
CVE
CVE-2025-12718
View all Quick Contact Form vulnerabilities

At a glance

CVE-2025-12718 is a medium-severity Improper Input Validation vulnerability in the Quick Contact Form WordPress plugin, affecting versions <= 8.2.6. It carries a CVSS score of 5.8 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 8.2.7; sites on affected versions should update now. Disclosed January 2026, reported by Md. Moniruzzaman Prodhan (NomanProdhan).

Vulnerability Overview

The Quick Contact Form plugin for WordPress is vulnerable to Open Mail Relay in all versions up to, and including, 8.2.6. This is due to the 'qcf_validate_form' AJAX endpoint allowing a user controlled parameter to set the 'from' email address. This makes it possible for unauthenticated attackers to send emails to arbitrary recipients utilizing the server. The information is limited to the contact form submission details.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-20: Improper Input Validation

Quick Contact Form <= 8.2.6 carries this weakness at qcf_validate_form, and reaching it takes no account at all. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.

The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For Quick Contact Form the fix is 8.2.7: builds <= 8.2.6 are affected, anything from 8.2.7 onward is not.

Remediation

Update to version 8.2.7, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Quick Contact Form 8.2.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C