dbcve.org
Canaldenuncia.appApplication · Canaldenuncia

CVE-2025-41339

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_sociedad' in '/backend/api/buscarTipoDenuncia.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 · moderate confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in the buscarTipoDenuncia.php API endpoint. The application fails to validate that the user is authorized to access the specific 'id_sociedad' (society/organization ID) provided in the POST request, allowing any user to query and retrieve information belonging to other users by manipulating this parameter.

MitigationImplement proper authorization checks to verify the requesting user owns or has permission to access the specific 'id_sociedad' before returning any data. Additionally, enforce session-based access controls tying each user to their permitted societies.

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 installed Canaldenuncia.app version
    Locate the version file or header in the Canaldenuncia application installation (common locations include version.php, VERSION file, or the application dashboard), or query the application metadata endpoint if available
    Affected if The installed version is below 4.4.8
  2. Locate the vulnerable buscarTipoDenuncia.php endpoint
    Search the web root directory for the file 'buscarTipoDenuncia.php' - this is typically found in the API or endpoints subdirectory of the Canaldenuncia application
    Affected if The file exists in the application structure
  3. Inspect how the id_sociedad parameter is handled
    Open buscarTipoDenuncia.php and examine the code that processes the 'id_sociedad' POST parameter - look for authorization checks, session validation, or ownership verification before querying or returning data
    Affected if The code directly uses the id_sociedad from the POST request without verifying the current user has permission to access that specific society ID
  4. Test for IDOR vulnerability (if authorized)
    Using an authenticated user account, send a POST request to buscarTipoDenuncia.php with a different id_sociedad value than the one assigned to your session - observe if the application returns data for a society the user does not belong to
    Affected if The application returns data for an id_sociedad that is not associated with the authenticated user's session
  5. Check session-to-society binding
    Examine how the application binds user sessions to societies - verify if the session or user profile stores the allowed id_sociedad values and if the endpoint validates against this list before returning data
    Affected if The application does not enforce that the requesting user can only access their assigned id_sociedad values

A user is affected if they are running Canaldenuncia.app version below 4.4.8 AND the buscarTipoDenuncia.php endpoint exists with id_sociedad parameter handling that lacks proper authorization validation.

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 permission to access the specific 'id_sociedad' before returning any data. Additionally, enforce session-based access controls tying each user to their permitted societies.

Recommended fix Moderate 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/buscarTipoDenuncia.php endpoint now properly enforces authorization checks
  3. Confirm that the 'id_sociedad' parameter cannot be manipulated to access other users' information without proper authentication

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
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,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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