CVE-2026-24619
BaseFortify
Publication date: 2026-01-23
Last updated on: 2026-04-28
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| popcash | popcash_net_code_integration_tool | to 1.8 (inc) |
Helpful Resources
Exploitability
| 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 PopCash.Net Code Integration Tool WordPress plugin (versions up to 1.8). It occurs due to missing authorization, authentication, or nonce token checks in certain functions, which allows unauthenticated users to perform actions that should require higher privileges. [1]
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized users performing privileged actions within the plugin, potentially compromising the security of the system. Although it has a low severity impact (CVSS score 5.3) and is considered unlikely to be exploited, it still poses a risk of unauthorized access due to improper access control. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves checking for unauthorized access attempts or actions performed without proper authentication in the PopCash.Net Code Integration Tool plugin. Since the issue is due to missing authorization checks, monitoring web server logs for unusual requests to plugin endpoints or functions that require higher privileges may help. Specific commands are not provided in the available resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the PopCash.Net Code Integration Tool plugin functionalities by implementing manual access controls at the server or application level, such as IP whitelisting or disabling the plugin if not in use. Since no official fix or patched version is currently available, applying additional security measures to prevent unauthorized access is recommended. [1]