dbcve.org
Canaldenuncia.appApplication · Canaldenuncia

CVE-2025-41113

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_denuncia' in '/backend/api/buscarDenunciaByPin.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 CanalDenuncia.app where the /backend/api/buscarDenunciaByPin.php endpoint accepts a POST request with the 'id_denuncia' parameter but fails to verify that the authenticated user is authorized to access that specific complaint. An attacker can enumerate or manipulate the id_denuncia parameter to retrieve sensitive complaint information belonging to other users.

MitigationImplement proper authorization checks to verify the authenticated user owns or has permission to access the complaint identified by 'id_denuncia' before returning any data. Consider adding user context validation and proper session management.

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. Check application version
    Inspect the application's source files, configuration, or footer for a version number (look in package.json, config files, or the main index page). Compare against the affected range: versions prior to 4.4.8 are vulnerable.
    Affected if The installed version is Canaldenuncia.app and is less than 4.4.8
  2. Verify vulnerable endpoint exists
    Check if the file /backend/api/buscarDenunciaByPin.php exists in the web root or application directory.
    Affected if The file buscarDenunciaByPin.php exists and is accessible via HTTP/HTTPS
  3. Inspect authorization logic in the endpoint
    Review the PHP code in buscarDenunciaByPin.php. Look for any session validation, user ownership checks, or SQL WHERE clauses that verify id_denuncia belongs to the authenticated user.
    Affected if The endpoint does not validate that the authenticated user owns or is authorized to access the id_denuncia being requested (no user context or ownership check in the code)
  4. Test endpoint authorization behavior
    If you have access to the application, log in as User A, note a complaint id that belongs to User A, then attempt to submit a request with a different id_denunca that belongs to a different user. Observe if data is returned without an authorization error.
    Affected if The endpoint returns complaint data for an id_denuncia that does not belong to the authenticated user, indicating missing authorization checks

A user is affected if they are running Canaldenuncia.app version below 4.4.8 and the buscarDenunciaByPin.php endpoint does not verify user ownership before returning 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 proper authorization checks to verify the authenticated user owns or has permission to access the complaint identified by 'id_denuncia' before returning any data. Consider adding user context validation and proper session management.

Recommended fix High confidence

4.4.8 or later

  1. 1. Backup the current Canaldenuncia.app installation and database before proceeding with any changes
  2. 2. Obtain the fixed version (4.4.8 or later) from the official Canaldenuncia.app vendor or update channel
  3. 3. Deploy the updated version to replace the existing installation
  4. 4. After upgrading, verify that the /backend/api/buscarDenunciaByPin.php endpoint now properly enforces authorization checks
  5. 5. Test that users can only access their own complaint information and cannot view other users' data via the id_denuncia parameter

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

Fix this in Canaldenuncia.app Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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