CVE-2025-53295
Awaiting Analysis Awaiting Analysis - Queue
BaseFortify

Publication date: 2025-06-27

Last updated on: 2026-04-23

Assigner: Patchstack

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-06-27
Last Modified
2026-04-23
Generated
2026-05-07
AI Q&A
2025-06-27
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a Broken Access Control issue in the iCount Payment Gateway WordPress plugin (up to version 2.0.6). It occurs due to missing authorization, authentication, or nonce token checks in certain functions, which can allow unauthenticated users to perform actions that should be restricted to higher-privileged users. [1]


How can this vulnerability impact me? :

The vulnerability could allow unauthorized users to access and perform restricted actions within the iCount Payment Gateway plugin, potentially leading to unauthorized manipulation of payment functions. However, the risk is considered low severity (CVSS 5.3) and is unlikely to be widely exploited. Users should monitor for updates and consider incident response if compromise is suspected. [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

Detection involves monitoring for unauthorized access attempts or unusual activity targeting the iCount Payment Gateway plugin functions that lack proper authorization checks. Since the vulnerability allows unauthenticated users to perform privileged actions, inspecting web server logs for suspicious requests to the plugin endpoints may help. However, no specific detection commands or signatures are provided. Users should monitor for unusual access patterns or unexpected function calls related to the plugin. [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include applying virtual patching (vPatching) provided by Patchstack, which auto-mitigates the vulnerability without impacting performance. Since no official fix or updated plugin version is currently available, users should implement this virtual patching solution, monitor for updates, and consider professional incident response if compromise is suspected. [1]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart