Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-41336: CWE-862 Missing Authorization in CanalDenuncia CanalDenuncia.app

0
High
VulnerabilityCVE-2025-41336cvecve-2025-41336cwe-862
Published: Tue Nov 04 2025 (11/04/2025, 13:16:02 UTC)
Source: CVE Database V5
Vendor/Project: CanalDenuncia
Product: CanalDenuncia.app

Description

A lack of authorisation vulnerability has been detected in CanalDenuncia.app. This vulnerability allows an attacker to access other users' information by sending a POST through the parameter 'web' in '/backend/api/buscarConfiguracionParametros.php'.

AI-Powered Analysis

AILast updated: 11/04/2025, 13:37:06 UTC

Technical Analysis

CVE-2025-41336 is a vulnerability classified under CWE-862 (Missing Authorization) found in CanalDenuncia.app, a platform likely used for whistleblowing or internal reporting purposes. The flaw exists in the backend API endpoint '/backend/api/buscarConfiguracionParametros.php', specifically through the 'web' POST parameter. Due to missing authorization controls, an attacker can craft a POST request to this endpoint and retrieve information belonging to other users without any authentication or user interaction. The vulnerability has a CVSS 4.0 base score of 8.7, indicating high severity, with an attack vector of network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and a high impact on confidentiality (VC:H) but no impact on integrity or availability. The vulnerability was reserved in April 2025 and published in November 2025, with no patches or known exploits currently available. The lack of authorization checks means that sensitive user data managed by CanalDenuncia.app can be exposed to unauthorized parties, posing significant privacy and compliance risks. The vulnerability affects version '0' of the product, which may indicate an initial or early release version. The vulnerability is assigned by INCIBE, a Spanish cybersecurity agency, suggesting regional relevance. The absence of patches necessitates urgent mitigation efforts by organizations using this software.

Potential Impact

The primary impact of CVE-2025-41336 is the unauthorized disclosure of sensitive user information, which compromises confidentiality. For European organizations, especially those in regulated sectors such as finance, healthcare, or public administration, this could lead to violations of GDPR and other data protection laws, resulting in legal penalties and reputational damage. The exposure of whistleblower or internal reporting data could undermine trust in organizational compliance programs and discourage legitimate reporting of misconduct. Since the vulnerability requires no authentication or user interaction, exploitation can be automated and widespread, increasing the risk of large-scale data breaches. The integrity and availability of the system are not directly affected, but the breach of confidentiality alone is critical given the nature of the data likely handled by CanalDenuncia.app. The lack of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, as attackers may develop exploits rapidly once the vulnerability is public. European organizations relying on CanalDenuncia.app must consider the risk of targeted attacks and insider threats exploiting this vulnerability.

Mitigation Recommendations

1. Immediately implement strict authorization checks on the '/backend/api/buscarConfiguracionParametros.php' endpoint to ensure that users can only access their own data. 2. Conduct a thorough code review of all API endpoints to verify proper authorization controls are in place. 3. Employ web application firewalls (WAFs) to detect and block suspicious POST requests targeting the vulnerable parameter. 4. Monitor application logs for unusual access patterns or repeated requests to the affected endpoint. 5. If possible, restrict access to the API backend to trusted networks or VPNs until a patch is available. 6. Engage with the vendor or development team to prioritize the release of a security patch addressing this vulnerability. 7. Educate users and administrators about the risks and signs of exploitation. 8. Consider implementing additional data encryption at rest and in transit to minimize data exposure in case of unauthorized access. 9. Prepare an incident response plan specifically for potential data breaches involving this vulnerability. 10. Regularly update and audit the software to ensure no other authorization issues exist.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
INCIBE
Date Reserved
2025-04-16T09:57:02.393Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 690a0152dc8910934c3a8e91

Added to database: 11/4/2025, 1:36:18 PM

Last enriched: 11/4/2025, 1:37:06 PM

Last updated: 11/5/2025, 2:06:08 PM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats