dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-57976

MEDIUM · 5.3 CVSS v3.1 Published 2025-09-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 CardCom CardCom Payment Gateway woo-cardcom-payment-gateway allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects CardCom Payment Gateway: from n/a through <= 3.5.0.7.

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 CardCom Payment Gateway WordPress plugin allows attackers to access functionality that should require proper access control due to incorrectly configured security levels. The plugin fails to properly validate user permissions before allowing access to sensitive payment gateway operations.

MitigationImplement proper capability checks and authorization validation on all plugin functions, particularly administrative and payment-related endpoints. Users should update to the latest version once the vendor releases a patch.

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 CardCom Payment Gateway plugin is installed
    Check if the 'cardcom-payment-gateway' directory exists in wp-content/plugins/ on your WordPress server, or list installed plugins via WP-CLI: wp plugin list --name='cardcom-payment-gateway'
    Affected if The plugin directory or listing confirms CardCom Payment Gateway is active on the site
  2. Identify installed plugin version
    Read the main plugin file (usually cardcom-payment-gateway.php) in the plugin directory and locate the 'Version' header comment, or use WP-CLI: wp plugin get cardcom-payment-gateway --field=version
    Affected if The version retrieved is lower than the patched version released by the vendor (compare against any official changelog or security advisory)
  3. Check for unprotected AJAX endpoints
    Examine the plugin's PHP files for registered AJAX actions (add_action('wp_ajax_...')) and verify whether each action includes current_user_can() or capability checks before executing sensitive operations; grep for 'wp_ajax_' in the plugin directory
    Affected if AJAX handlers handling payment or administrative functions lack capability verification (no current_user_can() call before processing the request)
  4. Inspect admin page access controls
    Review plugin files for admin menu registration (add_menu_page, add_submenu_page) and check if callback functions invoke proper authorization checks; look for pages handling payment gateway settings or transactions
    Affected if Admin pages performing sensitive payment operations execute without verifying user capabilities or nonces
  5. Test sensitive function authorization
    Analyze key payment-handling functions in the plugin (such as those processing payments, refunds, or configuration updates) to confirm they validate user permissions before execution
    Affected if Functions that create, modify, or delete payment records or gateway settings can be invoked by any authenticated user regardless of role

You are affected if the CardCom Payment Gateway plugin is installed with a version lacking the vendor's authorization patch, and sensitive payment operations can be accessed without proper capability validation.

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 capability checks and authorization validation on all plugin functions, particularly administrative and payment-related endpoints. Users should update to the latest version once the vendor releases a patch.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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