dbcve.org
Canaldenuncia.appApplication · Canaldenuncia

CVE-2025-41340

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_tp_denuncia' and 'id_sociedad' in '/backend/api/buscarTipoDenunciabyId.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 where the backend API endpoint '/backend/api/buscarTipoDenunciabyId.php' lacks proper authorization checks. An unauthenticated or authenticated attacker can access other users' sensitive information by manipulating the 'id_tp_denuncia' and 'id_sociedad' parameters in POST requests.

MitigationImplement proper session-based authorization checks to verify the requesting user has permission to access the specific complaint type (id_tp_denuncia) and society (id_sociedad) data before returning any information.

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 version
    Locate the version file or check the admin panel footer for the installed version number. Common paths include version.php, a config file, or the About section in the admin interface.
    Affected if The installed version is below 4.4.8 (e.g., 4.4.7, 4.4.6, etc.)
  2. Verify the vulnerable endpoint exists
    Check if the file /backend/api/buscarTipoDenunciabyId.php exists in the web root or application directory. This can be done via file system inspection or a GET request to the path.
    Affected if The endpoint file exists and is accessible via HTTP/HTTPS
  3. Confirm the vulnerable parameters are accepted
    Review the source code of buscarTipoDenunciabyId.php to verify it accepts POST parameters named 'id_tp_denuncia' and 'id_sociedad' without performing authorization validation.
    Affected if The endpoint processes id_tp_denuncia and id_socidad parameters without checking if the requesting user owns or has permission to access that data
  4. Check for authorization logic in the endpoint
    Inspect the PHP code in buscarTipoDenunciabyId.php to determine if session validation or ownership checks exist before returning complaint type or society data.
    Affected if No session-based user verification or ownership validation is performed before returning data
  5. Test endpoint accessibility
    Send a POST request to the endpoint (even with invalid or placeholder values) and observe if the application returns a response rather than rejecting the request due to authentication.
    Affected if The endpoint responds to requests without requiring proper authentication or authorization

If running Canaldenuncia.app version 4.4.7 or lower and the buscarTipoDenunciabyId.php endpoint is present and processes requests without authorization checks, the environment is affected by this IDOR vulnerability.

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 session-based authorization checks to verify the requesting user has permission to access the specific complaint type (id_tp_denuncia) and society (id_sociedad) data before returning any information.

Recommended fix Moderate confidence

Upgrade to Canaldenuncia.app version 4.4.8 or later

  1. 1. Contact the vendor (CanalDenuncia.app) to obtain version 4.4.8 or the latest stable release.
  2. 2. Before upgrading, perform a full backup of the current installation including database and configuration files.
  3. 3. Review the upgrade documentation provided by the vendor for any specific prerequisites.
  4. 4. Apply the upgrade to the Canaldenuncia.app installation.
  5. 5. After upgrade, verify the fix by testing that the /backend/api/buscarTipoDenunciabyId.php endpoint now properly enforces authorization checks.
  6. 6. Confirm that unauthenticated or unauthorized requests with 'id_tp_denuncia' and 'id_sociedad' parameters are rejected.

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