dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-37969

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-13
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 The African Boss Checkout with Zelle on Woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Checkout with Zelle on Woocommerce: from n/a through 3.1.

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 the Checkout with Zelle plugin for WooCommerce allows attackers to exploit incorrectly configured access control security levels. This likely enables unauthorized access to checkout functions or admin capabilities that should require proper authentication and authorization checks.

MitigationImplement proper role-based access control (RBAC) and authorization checks at all sensitive endpoints and functions within the plugin, ensuring users can only access resources and actions permitted by their assigned roles.

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. Verify Checkout with Zelle plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Checkout with Zelle' or 'Checkout with Zelle for WooCommerce' in the list
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    Click on the plugin name in the WordPress plugins list to view details, or check the plugin header in the main PHP file located in wp-content/plugins/checkout-with-zelle/
    Affected if The version displayed cannot be compared to a fixed safe version (no patch version specified)
  3. Confirm WooCommerce is active
    Check that WooCommerce is enabled in WordPress admin > Plugins, as this plugin extends WooCommerce functionality
    Affected if WooCommerce is active and the Checkout with Zelle plugin is installed
  4. Test for unauthorized admin access
    Attempt to access WooCommerce Zelle settings pages or checkout configuration endpoints without proper admin authentication using a browser incognito window
    Affected if Settings pages or checkout configuration loads without requiring login or displays sensitive Zelle configuration options without authorization
  5. Review access control configuration
    Check WordPress user roles in admin > Users > Roles, and verify if the plugin creates custom roles or modifies capability checks
    Affected if Custom roles or capabilities related to Zelle checkout exist that were not intentionally created by administrators

If the Checkout with Zelle plugin is installed and its settings or checkout functions are accessible without proper WordPress authentication or admin authorization, the environment is likely affected by this missing authorization vulnerability.

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

Implement proper role-based access control (RBAC) and authorization checks at all sensitive endpoints and functions within the plugin, ensuring users can only access resources and actions permitted by their assigned roles.

Recommended fix Moderate confidence

Version 3.2 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Checkout with Zelle on Woocommerce' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload the updated version
  6. 6. After updating, verify the plugin is functioning correctly and test the checkout process

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-2023-37969 — 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-37969 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