dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-53295

MEDIUM · 5.3 CVSS v3.1 Published 2025-06-27
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 iCount iCount Payment Gateway icount allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects iCount Payment Gateway: from n/a through <= 2.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 iCount Payment Gateway WordPress plugin allows users to access functionality that is not properly constrained by Access Control Lists (ACLs). This broken access control issue enables unauthorized access to certain plugin functions that should require proper capability checks or authentication.

MitigationUpdate to the latest version of the iCount Payment Gateway plugin when available. Until then, audit the plugin code to identify all functions lacking proper authorization checks and add capability checks, nonce validation, or permission callbacks to restrict access to administrative or authorized users only.

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. Confirm iCount Payment Gateway plugin is installed
    Navigate to WordPress admin dashboard > Plugins and verify iCount Payment Gateway appears in the installed plugins list, or check the filesystem at wp-content/plugins/ for an icount-payment-gateway folder
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually icount-payment-gateway.php) and locate the version defined in the plugin header comment, or check the WordPress plugins admin page version column
    Affected if The installed version matches any version of the iCount Payment Gateway plugin prior to the patched release
  3. Inspect plugin PHP files for missing capability checks
    Search all PHP files in the plugin directory for functions that perform sensitive operations (database changes, settings modifications, payment processing) and verify each contains a current_user_can() call or similar authorization check at the function entry point
    Affected if Any function handling sensitive operations lacks a current_user_can() or permission_callback check
  4. Check AJAX handlers for authorization
    Examine files registering add_action calls with 'wp_ajax_' hooks; for each AJAX callback, verify it includes proper capability verification or nonce validation before processing the request
    Affected if AJAX action handlers do not validate user capabilities before executing
  5. Review admin menu and page callbacks for access control
    Look for add_menu_page, add_submenu_page, or admin_page_parent declarations and trace the callback functions to confirm they verify user permissions before displaying sensitive information or performing actions
    Affected if Admin page callbacks lack capability checks and are accessible to low-privilege users

A user is affected if the iCount Payment Gateway plugin is installed with any version lacking the authorization fix and contains functions or AJAX handlers that process sensitive operations without verifying user capabilities.

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 to the latest version of the iCount Payment Gateway plugin when available. Until then, audit the plugin code to identify all functions lacking proper authorization checks and add capability checks, nonce validation, or permission callbacks to restrict access to administrative or authorized users only.

Recommended fix Moderate confidence

Update to the latest version of iCount Payment Gateway (version higher than 2.0.7)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the iCount Payment Gateway plugin
  4. 4. Check the current installed version (should be <= 2.0.7)
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Verify the update completed successfully
  7. 7. Test the payment gateway functionality to ensure the plugin still works correctly after updating

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 / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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