dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-51672

HIGH · 7.5 CVSS v3.1 Published 2024-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 FunnelKit FunnelKit Checkout.This issue affects FunnelKit Checkout: from n/a through 3.10.3.

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

Missing Authorization vulnerability in FunnelKit Checkout plugin for WooCommerce. The vulnerability allows unauthenticated or unauthorized users to access certain functionality that should require proper authentication or capability checks. The exact endpoint or function is not specified, but authorization bypasses in checkout plugins typically allow access to admin actions, user order data, or checkout process manipulation.

MitigationUpdate FunnelKit Checkout to version 3.10.4 or later which contains the authorization fix. Until patched, consider restricting access to the site's admin area and monitoring for suspicious checkout-related API activity.

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
None
Availability
High

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

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 FunnelKit Checkout is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'FunnelKit Checkout' or 'FunnelKit' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder starting with 'funnelkit'.
    Affected if FunnelKit Checkout plugin is present on the WordPress site
  2. Check the installed FunnelKit version
    In WordPress admin, find FunnelKit Checkout in the Plugins list and note the version number displayed under the plugin name. Or check the plugin's main PHP file header for the Version field.
    Affected if The installed version is lower than 3.10.4 (the fixed version)
  3. Verify unauthenticated access to checkout endpoints
    Test accessing common FunnelKit API endpoints without authentication (such as /?rest_route=/funnelkit/v1/ or /?rest_route=/funnelkit/v2/ endpoints) using a browser or curl tool. Check if requests return successful data without providing auth credentials.
    Affected if Requests to checkout-related REST API endpoints return 200 OK with data instead of 401/403 authentication errors
  4. Review access logs for suspicious checkout plugin activity
    Examine web server access logs (Apache/Nginx) and WordPress debug logs for repeated requests to /wp-json/funnelkit/ endpoints from unfamiliar IP addresses, especially if those requests access admin or user-specific functions without logged-in sessions.
    Affected if Logs show access to funnelkit-related endpoints from unauthenticated sources or unexpected IP addresses

You are affected if FunnelKit Checkout plugin is installed with a version before 3.10.4 and unauthenticated access to its endpoints is possible.

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 FunnelKit Checkout to version 3.10.4 or later which contains the authorization fix. Until patched, consider restricting access to the site's admin area and monitoring for suspicious checkout-related API activity.

Recommended fix Moderate confidence

Version newer than 3.10.3 (check WordPress plugin repository for latest stable release)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Update FunnelKit Checkout to the latest available version
  3. 3. Verify the update was successful by checking the plugin version in WordPress admin
  4. 4. Test checkout functionality to ensure the update did not break any features
  5. 5. Confirm the authorization vulnerability is resolved by verifying that proper authorization checks are in place for sensitive checkout operations

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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