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-41114: CWE-862 Missing Authorization in CanalDenuncia CanalDenuncia.app

0
High
VulnerabilityCVE-2025-41114cvecve-2025-41114cwe-862
Published: Tue Nov 04 2025 (11/04/2025, 13:10:31 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 parameters 'id_denuncia' and 'id_user' in '/backend/api/buscarDocumentosByIdDenunciaUsuario.php'.

AI-Powered Analysis

AILast updated: 11/04/2025, 13:25:35 UTC

Technical Analysis

CVE-2025-41114 is a missing authorization vulnerability classified under CWE-862 affecting CanalDenuncia.app, a platform likely used for whistleblowing or complaint management. The vulnerability arises because the backend API endpoint '/backend/api/buscarDocumentosByIdDenunciaUsuario.php' accepts POST requests with parameters 'id_denuncia' and 'id_user' but does not enforce authorization checks to verify that the requesting user is permitted to access the requested data. This lack of access control allows an attacker to craft POST requests with arbitrary 'id_denuncia' and 'id_user' values to retrieve documents or information belonging to other users without authentication or any user interaction. The vulnerability has a CVSS 4.0 base score of 8.7, indicating high severity due to network attack vector, no required privileges or user interaction, and a high impact on confidentiality. The vulnerability was reserved in April 2025 and published in November 2025, with no known exploits in the wild as of now. The absence of patches or mitigations from the vendor suggests that organizations must implement their own controls. The flaw compromises confidentiality severely, as sensitive whistleblower or complaint data could be exposed, potentially leading to privacy violations, reputational damage, and regulatory penalties. The vulnerability affects version 0 of the product, which may indicate an early or initial release. The technical details confirm the vulnerability is straightforward to exploit remotely without authentication, making it a critical risk for any deployment of CanalDenuncia.app.

Potential Impact

For European organizations, the impact of CVE-2025-41114 is significant due to the sensitive nature of data typically handled by whistleblowing platforms like CanalDenuncia.app. Unauthorized access to complaint or denunciation documents can lead to breaches of personal data protected under GDPR, resulting in legal and financial penalties. Confidentiality loss can undermine trust in whistleblowing mechanisms, discouraging legitimate reporting and harming organizational transparency. The exposure of sensitive information could also lead to targeted attacks, blackmail, or reputational damage. Since the vulnerability requires no authentication and can be exploited remotely, it broadens the attack surface considerably. Organizations relying on CanalDenuncia.app for compliance or internal reporting must consider this a critical threat to data privacy and integrity. The lack of known exploits in the wild provides a window for proactive mitigation, but the high CVSS score and ease of exploitation necessitate urgent action. Additionally, regulatory bodies in Europe may scrutinize affected organizations more closely if breaches occur due to this vulnerability.

Mitigation Recommendations

To mitigate CVE-2025-41114, organizations should immediately implement strict authorization checks on the '/backend/api/buscarDocumentosByIdDenunciaUsuario.php' endpoint to ensure that users can only access documents associated with their own 'id_user' and authorized 'id_denuncia' values. This includes validating session tokens or authentication credentials and enforcing role-based access control (RBAC) or attribute-based access control (ABAC) mechanisms. If vendor patches become available, they should be applied without delay. In the absence of patches, organizations should consider deploying web application firewalls (WAFs) with custom rules to detect and block suspicious POST requests containing unauthorized parameter values. Logging and monitoring of API access should be enhanced to detect anomalous access patterns indicative of exploitation attempts. Additionally, organizations should review and minimize data exposure in API responses and consider encrypting sensitive data at rest and in transit. Conducting security audits and penetration testing focused on authorization logic can help identify similar weaknesses. Finally, user awareness and incident response plans should be updated to address potential data breaches stemming from this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 6909fc133cfa4baba4c198bd

Added to database: 11/4/2025, 1:13:55 PM

Last enriched: 11/4/2025, 1:25:35 PM

Last updated: 11/5/2025, 7:34:38 AM

Views: 8

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