dbcve.org
Canaldenuncia.appApplication · Canaldenuncia

CVE-2025-41114

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/buscarDocumentosByIdDenunciaUsuario.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 Insecure Direct Object Reference (IDOR) vulnerability in the API endpoint /backend/api/buscarDocumentosByIdDenunciaUsuario.php. The application fails to verify that the authenticated user is authorized to access the documents associated with the provided 'id_denuncia' and 'id_user' parameters, allowing any authenticated user to view other users' sensitive information.

MitigationImplement proper authorization checks to validate that the requesting user has permission to access the specific complaint and user documents before returning any data. Use the authenticated user's session to verify ownership or proper access rights.

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 product and version
    Identify the installed version of Canaldenuncia Canaldenuncia.app. Check configuration files, version manifests, or admin panels for the version number.
    Affected if The installed version is below 4.4.8 (e.g., 4.4.7, 4.4.6, etc.)
  2. Locate vulnerable endpoint
    Check if the file /backend/api/buscarDocumentosByIdDenunciaUsuario.php exists in the deployed application.
    Affected if The vulnerable PHP file is present in the application directory.
  3. Verify API accepts id_denuncia and id_user parameters
    Review the endpoint's source code or test the API with a GET/POST request including 'id_denuncia' and 'id_user' parameters.
    Affected if The endpoint accepts these parameters without additional ownership verification.
  4. Test for IDOR vulnerability
    Authenticate as a test user, then attempt to access documents using an id_denuncia or id_user value that belongs to a different user.
    Affected if The API returns sensitive documents belonging to other users without verifying the authenticated user owns or has permission to access that data.

A user is affected if they run Canaldenuncia Canaldenuncia.app version below 4.4.8 and the API endpoint returns other users' documents when given arbitrary id_denuncia and id_user parameter values.

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 proper authorization checks to validate that the requesting user has permission to access the specific complaint and user documents before returning any data. Use the authenticated user's session to verify ownership or proper access rights.

Recommended fix Moderate confidence

4.4.8 or later

  1. Upgrade Canaldenuncia.app to version 4.4.8 or later to resolve the missing authorization vulnerability
  2. After upgrading, verify that the /backend/api/buscarDocumentosByIdDenunciaUsuario.php endpoint properly enforces authorization checks for the 'id_denuncia' and 'id_user' parameters

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

Fix this in Canaldenuncia.app Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41114 — 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-41114 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