dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-67571

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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
Missing Authorization vulnerability in WPFunnels WPFunnels wpfunnels allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WPFunnels: from n/a through <= 3.6.2.

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 · moderate confidence

The WPFunnels WordPress plugin through version 3.6.2 contains a missing authorization vulnerability allowing exploitation of incorrectly configured access control security levels. This could permit unauthenticated or unauthorized users to access or modify funnel-related data and settings they should not have permission to access.

MitigationUpdate WPFunnels to the latest version when a patch is released, or implement proper capability checks and nonce validation on all affected plugin functions that handle sensitive operations.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm WPFunnels plugin is installed
    Navigate to WordPress admin > Plugins, or check /wp-content/plugins/ directory for a folder named 'wpfunnels' or similar. Also check for files like 'wpfunnels.php' in the plugins directory.
    Affected if The plugin folder exists in the WordPress plugins directory and contains the plugin files.
  2. Verify WPFunnels plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and check if WPFunnels shows as 'Active'. Alternatively, query the wp_options table for option_name = 'active_plugins' and check if WPFunnels is listed.
    Affected if The plugin is installed and currently active on the WordPress site.
  3. Determine installed WPFunnels version
    Check the plugin main file header (e.g., wpfunnels.php) for the 'Version' comment, or view the plugin in WordPress admin plugins list where the version is displayed, or query the wp_options table for option_name containing 'wpfunnels_version'.
    Affected if The installed version is 3.6.2 or any earlier version (the vulnerability affects through 3.6.2).
  4. Check for public-facing funnel endpoints
    Inspect the site's public URLs for funnel-related paths such as /funnel/, /wpfunnels/, /funnels/, or any custom endpoints registered by the plugin. These are accessible without authentication if the vulnerability exists.
    Affected if Funnel-related public endpoints are accessible without requiring login or authorization checks.

The environment is affected if WPFunnels plugin is installed, active, and running version 3.6.2 or earlier, with public-facing endpoints that lack proper authorization controls.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WPFunnels to the latest version when a patch is released, or implement proper capability checks and nonce validation on all affected plugin functions that handle sensitive operations.

Recommended fix Moderate confidence

Latest available version of WPFunnels (version higher than 3.6.2)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate WPFunnels in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. After updating, verify the plugin is running on a version higher than 3.6.2
  6. 6. Test critical funnel flows to ensure functionality is intact

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67571 — 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-67571 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