dbcve.org
Canaldenuncia.appApplication · Canaldenuncia

CVE-2025-41341

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 'seguro' in '/backend/api/buscarUsuarioByDenuncia.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 CanalDenuncia.app where the /backend/api/buscarUsuarioByDenuncia.php endpoint accepts POST parameters 'id_denuncia' and 'seguro' without verifying that the authenticated user is authorized to access the specified complaint record. An attacker can enumerate the id_denuncia parameter to retrieve other users' personal information.

MitigationImplement proper authorization checks to verify the requesting user owns or has rights to access the specific complaint identified by id_denuncia before returning any user data. Consider adding consistent authentication middleware across all API endpoints.

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. Identify installed Canaldenuncia version
    Check version file or config: look for version.php, VERSION.txt, or version info in config files within the Canaldenuncia.app installation directory. Also check the application's footer or admin panel for version display.
    Affected if The installed version is below 4.4.8
  2. Locate the vulnerable endpoint file
    Verify the existence of /backend/api/buscarUsuarioByDenuncia.php in your web server's document root for the Canaldenuncia application.
    Affected if The file exists and the application version is below 4.4.8
  3. Inspect the endpoint for authorization logic
    Open buscarUsuarioByDenuncia.php and search for session verification, user ownership validation, or access control checks before processing the id_denuncia parameter. Look for functions like checkOwnership, verifyUser, or similar that validate the requesting user has rights to the complaint.
    Affected if No authorization or ownership check exists before retrieving user data by id_denuncia
  4. Check API authentication middleware
    Examine if the /backend/api/ directory has a common include file (such as auth.php or session.php) that provides centralized authentication, and whether buscarUsuarioByDenuncia.php includes and enforces it.
    Affected if The endpoint lacks consistent authentication middleware or the middleware does not verify complaint ownership

You are affected if running Canaldenuncia.app version below 4.4.8 and the /backend/api/buscarUsuarioByDenuncia.php endpoint exists without proper authorization checks on the id_denuncia parameter.

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 owns or has rights to access the specific complaint identified by id_denuncia before returning any user data. Consider adding consistent authentication middleware across all API endpoints.

Recommended fix High confidence

Version 4.4.8 or latest stable release

  1. Obtain Canaldenunca.app version 4.4.8 or later from the vendor
  2. Backup the current Canaldenunca.app installation and database
  3. Upgrade the application to version 4.4.8 or the latest stable release
  4. Verify that the /backend/api/buscarUsuarioByDenuncia.php endpoint now properly enforces authorization checks
  5. Confirm that users can no longer access other users' information via the 'id_denuncia' and 'seguro' parameters

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-41341 — 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-41341 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