dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-62754

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-22
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 Kapil Paul Payment Gateway bKash for WC woo-payment-bkash allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Payment Gateway bKash for WC: from n/a through <= 3.1.0.

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 bKash payment gateway plugin for WooCommerce (woo-payment-bkash) allows attackers to exploit incorrectly configured access control security levels. This authorization bypass could enable unauthorized access to sensitive payment operations or administrative functions within the plugin.

MitigationImplement proper authorization checks on all sensitive plugin endpoints and functions; update to a patched version when available and apply web application firewall rules to mitigate unauthorized access in the interim.

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 if the bKash payment gateway plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'woo-payment-bkash' or similar bKash-related plugin directories. Alternatively, log into the WordPress admin panel and navigate to Plugins > Installed Plugins to look for any bKash payment gateway plugin.
    Affected if The plugin folder 'woo-payment-bkash' or a similarly named bKash payment plugin exists in the WordPress installation.
  2. Determine the installed plugin version
    If the plugin is found, open the main plugin file (usually named 'woo-payment-bkash.php') and locate the plugin header comment which contains the 'Version' field. Alternatively, view the plugin details in WordPress admin under Plugins > Installed Plugins.
    Affected if The installed version is unknown or cannot be compared to a patched version (the specific vulnerable version range was not provided in the CVE).
  3. Verify the plugin is active on the WooCommerce site
    In WordPress admin, check Plugins > Installed Plugins to confirm the bKash payment plugin shows as 'Active'. Alternatively, check WooCommerce > Settings > Payments to see if bKash is enabled as a payment gateway.
    Affected if The plugin is installed and active, meaning the vulnerable code is running on the site.
  4. Inspect access control configuration
    Navigate to WooCommerce > Settings > Payments > bkash (or the plugin's settings page if accessible). Look for any settings related to 'Access Control', 'Security Level', 'API Permissions', or 'Authorization' that may be set to an insecure level (such as 'No Authentication Required' or 'Public').
    Affected if Access control settings are configured to allow unauthenticated or unauthorized access to sensitive payment or administrative functions.
  5. Test for unauthorized endpoint access
    If the plugin exposes AJAX endpoints or admin pages (typically under /wp-admin/admin-ajax.php or /wp-admin/?page=bkash-settings), attempt to access these endpoints without logging in or without administrator privileges to see if they respond without returning an authorization error.
    Affected if Sensitive plugin endpoints return functional responses (rather than redirects to login or permission denied errors) when accessed by unauthenticated or low-privilege users.

Your environment is affected if the bKash payment gateway plugin for WooCommerce is installed and active, and sensitive payment or admin endpoints are accessible without proper authorization checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks on all sensitive plugin endpoints and functions; update to a patched version when available and apply web application firewall rules to mitigate unauthorized access in the interim.

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-62754 — 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-62754 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