CVE-2025-3780

WCFM – Frontend Manager for WooCommerce along with Bookings Subscription Listings Compatible <= 6.7.16 - Missing Authorization to Unauthenticated Plugin Settings Modification

Strategic Overview

Status
Patched in 6.7.17
Affected Version
<= 6.7.16
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-3780
View all WCFM – Frontend Manager for WooCommerce vulnerabilities

At a glance

CVE-2025-3780 is a medium-severity Missing Authorization vulnerability in the WCFM WordPress plugin, affecting versions <= 6.7.16. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.7.17; sites on affected versions should update now. Disclosed July 2025, reported by Brian Sans-Souci (liardom).

Vulnerability Overview

The WCFM – Frontend Manager for WooCommerce along with Bookings Subscription Listings Compatible plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the wcfm_redirect_to_setup function in all versions up to, and including, 6.7.16. This makes it possible for unauthenticated attackers to view and modify the plugin settings, including payment details and API keys

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 WCFM <= 6.7.16 takes no account at all. 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. For WCFM the fix is 6.7.17: builds <= 6.7.16 are affected, anything from 6.7.17 onward is not.

Remediation

Update to version 6.7.17, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WCFM 6.7.17 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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