dbcve.org
Canaldenuncia.appApplication · Canaldenuncia

CVE-2025-41111

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/buscarComentariosByDenuncia.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

The application lacks proper authorization checks on the /backend/api/buscarComentariosByDenuncia.php endpoint. By manipulating the id_denuncia parameter in a POST request, an attacker can access comments belonging to any complaint (denuncia) without ownership verification, enabling unauthorized information disclosure across users.

MitigationImplement proper authorization validation to ensure the authenticated user has permission to access the specific complaint's comments before returning data. This typically involves checking session credentials against the requested resource owner.

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 the installed version of Canaldenuncia
    Locate the version information in the application's source code, configuration files, or admin panel. Check files such as version.php, composer.json, or the main application header/footer for a version number.
    Affected if The installed version is lower than 4.4.8 (e.g., 4.4.7, 4.4.0, etc.)
  2. Confirm the vulnerable endpoint exists
    Check if the file /backend/api/buscarComentariosByDenuncia.php exists in the web application's backend directory structure.
    Affected if The file /backend/api/buscarComentariosByDenuncia.php is present in the deployment
  3. Verify authorization is missing on the endpoint
    Make a POST request to /backend/api/buscarComentariosByDenuncia.php with a valid id_denuncia parameter value that belongs to a different user or complaint. Use an authenticated session and observe if the response returns comments without verifying ownership.
    Affected if The endpoint returns comments for any id_denuncia value without verifying that the authenticated user owns or has permission to access that specific complaint's comments
  4. Check if the API lacks ownership validation
    Inspect the source code of buscarComentariosByDenuncia.php and look for session validation, user ownership checks, or SQL WHERE clauses that verify the logged-in user matches the complaint owner before returning data.
    Affected if The code does not validate that the authenticated user owns the complaint before returning its comments, or no user ID/session check is performed

The environment is affected if Canaldenuncia.app is installed at a version lower than 4.4.8 AND the /backend/api/buscarComentariosByDenuncia.php endpoint is accessible without proper ownership verification.

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 validation to ensure the authenticated user has permission to access the specific complaint's comments before returning data. This typically involves checking session credentials against the requested resource owner.

Recommended fix High confidence

4.4.8

  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/buscarComentariosByDenuncia.php endpoint properly enforces authorization checks for 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
  • 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-41111 — 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-41111 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