CVE-2026-66660

Contact Form 7 – PayPal & Stripe Add-on <= 2.5.1 - Missing Authorization

2026-08-11 00:00
dodoh4t

Strategic Overview

Status
Unpatched
Affected Plugin
Contact Form 7 – PayPal & Stripe Add-on
Affected Version
<= 2.5.1
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-66660
View all Contact Form 7 – PayPal & Stripe Add-on vulnerabilities

At a glance

CVE-2026-66660 is a medium-severity Missing Authorization vulnerability in the Contact Form 7 WordPress plugin, affecting versions <= 2.5.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2026, reported by dodoh4t.

Vulnerability Overview

The Contact Form 7 – PayPal & Stripe Add-on plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in versions up to, and including, 2.5.1. This makes it possible for unauthenticated attackers to perform an unauthorized action.

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-862: Missing Authorization

Reaching this weakness in Contact Form 7 <= 2.5.1 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. No fixed build of this plugin is recorded for Contact Form 7 yet, so installs running <= 2.5.1 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-66660https://www.wordfence.com/threat-intel/vulnerabilities/id/87ae0d66-3974-48ed-8a84-722e52df6b64https://nvd.nist.gov/vuln/detail/CVE-2026-66660

Related records

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