Skip to main content
VulnerabilityPublished

CVE-2025-41111: CanalDenuncia.app · Missing Authorization

Affects CanalDenuncia.appSource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
CanalDenuncia CanalDenuncia.appAffected
  • =0
Fixed in–

AI-suggested

  1. Immediately implement strict access control mechanisms on the '/backend/api/buscarComentariosByDenuncia.php' endpoint to ensure that only authorized users can query data related to their own 'id_denuncia'.
  2. Introduce robust authorization checks in the backend to validate user permissions before returning any data.
  3. Employ input validation and parameter sanitization to prevent unauthorized parameter manipulation.
  4. Enable detailed logging and monitoring of API requests to detect unusual access patterns or attempts to access other users' data.
  5. If possible, restrict API access via network segmentation or VPNs to trusted users only until a patch is released.
  6. Conduct a thorough security audit of the entire CanalDenuncia.app codebase to identify and remediate similar authorization issues.
  7. Educate users and administrators about the risk and encourage reporting of suspicious activity.
  8. Coordinate with the vendor for timely patch deployment once available.
  9. Consider deploying Web Application Firewalls (WAF) with custom rules to block suspicious POST requests targeting the vulnerable endpoint.
  10. Review and update privacy policies and incident response plans to prepare for potential data breach scenarios.

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 'id_denuncia' in '/backend/api/buscarComentariosByDenuncia.php'.

References

Community reviews

Loading reviews…