CVE-2025-41344
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 · uneditedA 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_archivo' in '/backend/api/verArchivo.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 confidenceThis is an Insecure Direct Object Reference (IDOR) vulnerability in CanalDenuncia.app's /backend/api/verArchivo.php endpoint. The application fails to verify that the authenticated user has proper authorization to access the file identified by the 'id_archivo' parameter in POST requests, allowing any authenticated user to view files belonging to other users.
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< 4.4.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify CanalDenuncia.app installation and versionLocate the CanalDenuncia application installation directory and check the version number in the application configuration, manifest, or version file. Compare against the affected range: versions < 4.4.8 are vulnerable.Affected if The installed version is CanalDenuncia Canaldenuncia.app with a version number less than 4.4.8
-
Verify verArchivo.php endpoint existsCheck if the file /backend/api/verArchivo.php exists in the web application root directory.Affected if The vulnerable endpoint file exists in the application structure
-
Inspect authorization logic in verArchivo.phpOpen verArchivo.php and examine the code handling the 'id_archivo' POST parameter. Look for database queries that retrieve file information and check whether the code verifies that the logged-in user owns or has permission to access the file before returning content.Affected if The code retrieves files by 'id_archivo' without validating that the authenticated user owns or is authorized to access that specific file record
-
Test the IDOR vulnerability (if authorized)With an authenticated user account, send a POST request to /backend/api/verArchivo.php with an 'id_archivo' parameter value that belongs to a different user. Observe whether the application returns the file content without rejecting the request.Affected if The endpoint returns file content for an 'id_archivo' belonging to another user without proper authorization validation
A user is affected if CanalDenuncia.app version is less than 4.4.8 AND the /backend/api/verArchivo.php endpoint exists AND the code fails to verify that the authenticated user owns the file identified by the 'id_archivo' parameter before returning content.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.4.8
Implement proper authorization checks in verArchivo.php to verify the requesting user owns or has permission to access the file identified by 'id_archivo' before returning any content.
4.4.8
- 1. Identify the current installed version of CanalDenuncia.app
- 2. Create a backup of the current installation and database
- 3. Upgrade CanalDenuncia.app to version 4.4.8 or later
- 4. Verify the upgrade was successful by checking the new version number
- 5. Test that the /backend/api/verArchivo.php endpoint now properly enforces authorization checks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41344 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-41344 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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