dbcve.org
Canaldenuncia.appApplication · Canaldenuncia

CVE-2025-41345

HIGH · 7.5 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to 4.4.8 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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/buscarDenunciasById.php'.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an IDOR (Insecure Direct Object Reference) vulnerability in the buscarDenunciasById.php endpoint where the application fails to verify that the requesting user has permission to access the complaint data identified by the id_denuncia and id_user parameters. An attacker can craft a POST request with arbitrary user identifiers to retrieve sensitive complaint information belonging to other users without proper authorization.

MitigationImplement server-side authorization checks to validate that the authenticated user has permission to access the specific complaint before returning data. Additionally, enforce proper session validation and consider implementing row-level access controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Canaldenuncia.appApplication
Affected:< 4.4.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Canaldenuncia.app installation
    Identify if Canaldenuncia.app is deployed in your environment. Check for the presence of the application web root directory and look for Canaldenuncia-specific files.
    Affected if The application is installed and running Canaldenuncia.app version below 4.4.8
  2. Locate the vulnerable endpoint
    Search for the file buscarDenunciasById.php in the web application directory structure. This is typically found within the PHP source code of the Canaldenuncia application.
    Affected if The file buscarDenunciasById.php exists in the application codebase
  3. Verify endpoint accessibility
    Test if the buscarDenunciaById.php endpoint is reachable via HTTP POST requests. Attempt a request to the endpoint path to confirm it responds.
    Affected if The endpoint is accessible and responds to HTTP requests
  4. Check for missing authorization logic
    Review the source code of buscarDenunciaById.php and inspect whether there are server-side authorization checks validating that the authenticated user has permission to access the complaint identified by id_denuncia and id_user parameters.
    Affected if The code lacks proper authorization validation before returning complaint data
  5. Confirm parameter acceptance
    Send a test POST request to the endpoint with id_denuncia and id_user parameters containing values for different users to verify the endpoint processes these parameters.
    Affected if The endpoint accepts id_denuncia and id_user parameters and returns data without verifying user ownership

Your environment is affected if Canaldenuncia.app below version 4.4.8 is installed and the buscarDenunciaById.php endpoint processes requests without validating that the authenticated user owns or has permission to access the specified complaint data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.4.8 or later
Fixed in 4.4.8
Interim mitigation

Implement server-side authorization checks to validate that the authenticated user has permission to access the specific complaint before returning data. Additionally, enforce proper session validation and consider implementing row-level access controls.

Recommended fix Moderate confidence

CanalDenuncia.app 4.4.8 or later

  1. 1. Verify current installation version of CanalDenuncia.app
  2. 2. Backup the current database and application files before upgrading
  3. 3. Obtain the updated version (4.4.8 or later) from the official vendor
  4. 4. Deploy the upgrade following the vendor's standard upgrade procedure
  5. 5. Verify the fix by testing that unauthorized access to other users' information is no longer possible via the /backend/api/buscarDenunciasById.php endpoint
  6. 6. Confirm proper authorization checks are in place for the 'id_denuncia' and 'id_user' parameters
Caveat Review release notes for any breaking changes between current version and 4.4.8

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Canaldenuncia.app Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-41345 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data