dbcve.org
Canaldenuncia.appApplication · Canaldenuncia

CVE-2025-41342

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 parameter 'id_user' in '/backend/api/buscarUsuarioId.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

A lack of authorization vulnerability in CanalDenuncia.app allows attackers to access other users' information by manipulating the 'id_user' parameter in a POST request to /backend/api/buscarUsuarioId.php. This is a classic Insecure Direct Object Reference (IDOR) where the API endpoint does not verify that the requesting user has permission to access the specified user data.

MitigationImplement proper authorization checks to verify the requesting user has permission to access the requested user data, typically by validating the session or token against the requested id_user parameter.

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 you are running Canaldenuncia Canaldenuncia.app
    Identify the web application by inspecting the application banners, footer, or by examining the HTTP responses. The application is typically deployed as a whistleblower platform.
    Affected if The application is Canaldenuncia Canaldenuncia.app
  2. Check the installed version
    Locate the version number in the application configuration files, about page, or by checking the source code. Common locations include config files, README files, or the main index page footer.
    Affected if The version is lower than 4.4.8
  3. Verify the vulnerable endpoint exists
    Check if the file /backend/api/buscarUsuarioId.php is present in the deployed application by attempting to access it or listing the backend/api directory contents.
    Affected if The file /backend/api/buscarUsuarioId.php exists and is accessible
  4. Test for IDOR vulnerability in the user lookup endpoint
    Send a POST request to /backend/api/buscarUsuarioId.php with an id_user parameter value different from your authenticated user ID. Compare your installed version to the affected ranges. Use an HTTP proxy or curl to inspect whether the API returns user data for the specified id_user without validating your session permissions.
    Affected if The API returns user information for an id_user that does not belong to the authenticated session without authorization errors

A user is affected if they are running Canaldenuncia Canaldenuncia.app version lower than 4.4.8 and the /backend/api/buscarUsuarioId.php endpoint returns other users' data without proper authorization validation.

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 verify the requesting user has permission to access the requested user data, typically by validating the session or token against the requested id_user parameter.

Recommended fix Moderate confidence

4.4.8 or later

  1. 1. Back up the current CanalDenuncia.app installation and database before making any changes
  2. 2. Obtain the CanalDenuncia.app version 4.4.8 or later from the official vendor
  3. 3. Follow the vendor's documented upgrade procedure to update the application
  4. 4. Verify that the '/backend/api/buscarUsuarioId.php' endpoint now properly enforces authorization checks
  5. 5. Test that users can only access their own information and not other users' data via the 'id_user' parameter
  6. 6. Confirm the application is functioning normally after the upgrade

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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