dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-12353

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-08
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
The WPFunnels – The Easiest Funnel Builder For WordPress And WooCommerce To Collect Leads And Increase Sales plugin for WordPress is vulnerable to unauthorized user registration in all versions up to, and including, 3.6.2. This is due to the plugin relying on a user controlled value 'optin_allow_registration' to determine if user registration is allowed, instead of the site-specific setting. This makes it possible for unauthenticated attackers to register new user accounts, even when user registration is disabled.

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 WPFunnels plugin for WordPress uses a user-supplied parameter 'optin_allow_registration' to determine whether to allow user account creation, rather than checking the WordPress site's native user registration settings. This allows unauthenticated attackers to bypass the site's registration controls and create new user accounts by supplying this parameter, even when registration is explicitly disabled.

MitigationUpdate the WPFunnels plugin to version 3.6.3 or later when available, and ensure WordPress user registration settings are properly enforced at the application level rather than trusting client-supplied values.

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. Identify WPFunnels plugin version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate WPFunnels, and note the version number displayed
    Affected if The installed version is lower than 3.6.3 (the patched version)
  2. Verify WordPress user registration setting
    In WordPress admin, go to Settings > General and check 'Membership: Anyone can register' - note whether it is unchecked (disabled) or checked (enabled)
    Affected if Registration is disabled in WordPress settings but the plugin may still accept the optin_allow_registration parameter to bypass this control
  3. Review created user accounts for anomalies
    In WordPress admin, go to Users > All Users and examine recently created accounts, particularly those with roles like Subscriber that may have been created without proper authorization
    Affected if New user accounts exist that were not intentionally created by administrators, especially in bulk or around the time the plugin was active
  4. Inspect plugin configuration files
    If filesystem access is available, examine the WPFunnels plugin files for code that directly processes the 'optin_allow_registration' parameter from user input without validating against WordPress registration settings
    Affected if The plugin code reads optin_allow_registration from request parameters and uses it to determine account creation behavior without server-side validation

A user is affected if they have WPFunnels installed with a version below 3.6.3 and the plugin's optin feature can be used to create user accounts despite WordPress registration being disabled

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 the WPFunnels plugin to version 3.6.3 or later when available, and ensure WordPress user registration settings are properly enforced at the application level rather than trusting client-supplied values.

Recommended fix Moderate confidence

Version 3.6.3 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate WPFunnels – The Easiest Funnel Builder For WordPress And WooCommerce To Collect Leads And Increase Sales
  4. Check if an update is available and update to the latest version (version 3.6.3 or later)
  5. Alternatively, navigate to Dashboard > Updates and check for plugin updates
  6. After updating, verify that user registration behaves according to the site-specific WordPress settings under Settings > General > Membership

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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