dbcve.org
Frontend Manager For Woocommerce Along With Bookings Subscription Listings CompatibleWordPress extension · Wclovers

CVE-2025-3780

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-09
Fix available
A fix is available. Upgrade to 6.7.17 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
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 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 · high confidence

The WCFM WordPress plugin fails to enforce authorization on the wcfm_redirect_to_setup function, allowing unauthenticated attackers to directly access and modify plugin settings. This broken access control vulnerability exposes sensitive configuration data including payment gateway details and API keys.

MitigationUpdate to version 6.7.17 or later; if no patch is available, disable the plugin and rotate any exposed credentials immediately.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Frontend Manager For Woocommerce Along With Bookings Subscription Listings CompatibleWordPress extension
Affected:< 6.7.17

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if WCFM plugin is installed
    Check the WordPress wp-content/plugins/ directory for the 'wc-frontend-manager' or similar WCFM-related plugin folder. Alternatively, query the WordPress database wp_options table for option_name containing 'wcfm' or check via WP-CLI: wp plugin list --name='*wcfm*'
    Affected if The WCFM plugin folder exists in the WordPress plugins directory or is listed in the WordPress plugin registry
  2. Determine installed plugin version
    Locate the main plugin PHP file (usually wp-content/plugins/wc-frontend-manager/wc-frontend-manager.php) and read the Version header from the plugin file comment block, or query via WP-CLI: wp plugin get wc-frontend-manager --field=version
    Affected if The installed version is lower than 6.7.17 (e.g., 6.7.16, 6.7.10, etc.)
  3. Verify vulnerable function exists in codebase
    Search the plugin files for the function 'wcfm_redirect_to_setup' using grep or a file search within the plugin directory. Check if the function lacks authorization checks (look for capability checks or nonce verification before executing sensitive operations)
    Affected if The wcfm_redirect_to_setup function exists and contains no access control validation (missing current_user_can() or wp_verify_nonce() calls before processing settings)
  4. Inspect plugin settings for unauthorized modifications
    Query the WordPress wp_options table for wcfm-related options (e.g., SELECT * FROM wp_options WHERE option_name LIKE 'wcfm_%'), or navigate to WP Admin > WCFM > Settings and review all configuration panels including payment gateway settings, API credentials, and any sensitive configuration fields
    Affected if Settings contain unexpected values, new payment gateway configurations were added, or API keys/credentials appear modified without admin action

You are affected if the WCFM plugin is installed with a version lower than 6.7.17 and the wcfm_redirect_to_setup function is accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 6.7.17 or later
Fixed in 6.7.17
Interim mitigation

Update to version 6.7.17 or later; if no patch is available, disable the plugin and rotate any exposed credentials immediately.

Recommended fix High confidence

6.7.17

  1. Backup your WordPress site before making any changes
  2. Update the WCFM – Frontend Manager for WooCommerce along with Bookings Subscription Listings Compatible plugin to version 6.7.17 or later through the WordPress admin dashboard (Plugins > All Plugins > WCFM > Update Now) or via wp-cli: wp plugin update wcmarketplace-frontend-manager
  3. Verify the update was successful by checking the plugins page shows version 6.7.17 or higher
  4. After updating, review plugin settings (especially payment configurations and API keys) to ensure no unauthorized changes were made

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Frontend Manager For Woocommerce Along With Bookings Subscription Listings Compatible Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3780 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3780 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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