dbcve.org
Canaldenuncia.appApplication · Canaldenuncia

CVE-2025-41335

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' and ' 'id_sociedad' in '/api/buscarEmpresaById.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 the /api/buscarEmpresaById.php endpoint. The application fails to validate user authorization before returning data, allowing an attacker to access other users' information by manipulating the 'id' and 'id_sociedad' parameters in a POST request.

MitigationImplement proper authorization checks in the API endpoint to verify the requesting user has permission to access the requested data object 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. Identify Canaldenuncia installation and version
    Locate the Canaldenuncia.application files or check the application's version information, typically found in configuration files, README, or the application dashboard. Compare the installed version against the affected range: versions below 4.4.8 are vulnerable.
    Affected if Installed version is lower than 4.4.8
  2. Verify the vulnerable endpoint exists
    Check if the file /api/buscarEmpresaById.php exists in the web application's document root or API directory. This endpoint must be present for the vulnerability to be exploitable.
    Affected if The /api/buscarEmpresaById.php file exists in the application
  3. Confirm the API lacks authorization checks
    Examine the source code of /api/buscarEmpresaById.php to verify whether it validates user permissions before returning data. Look for session checks, role verification, or ownership validation logic before processing the 'id' and 'id_sociedad' parameters.
    Affected if The endpoint returns data without validating that the requesting user owns or has permission to access the specified 'id' and 'id_sociedad' values
  4. Test parameter manipulation access
    If authorized to test, send a POST request to /api/buscarEmpresaById.php with an 'id' and 'id_sociedad' value belonging to a different user than the authenticated session. Successful retrieval of unauthorized data confirms the vulnerability.
    Affected if The API returns data for an 'id' or 'id_sociedad' that does not belong to the authenticated user

The environment is affected if Canaldenuncia version is below 4.4.8 AND the /api/buscarEmpresaById.php endpoint returns data without validating user ownership of the requested 'id' and 'id_sociedad' parameters.

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 in the API endpoint to verify the requesting user has permission to access the requested data object before returning any information.

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 /api/buscarEmpresaById.php endpoint now properly enforces authorization checks before returning user information
  3. Test that users can only access their own data and cannot retrieve other users' information by manipulating the 'id' and 'id_sociedad' parameters
  4. Confirm the vulnerability is no longer exploitable by attempting to access data belonging to other users

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 / QA3.0 h
19.0 hours of engineering $3,380
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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