CanalDenuncia.app up to 4.4.7 buscarTestigoByIdDenunciaUsuario.php id_denuncia authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in CanalDenuncia.app up to 4.4.7. It has been classified as problematic. The affected element is an unknown function of the file /backend/api/buscarTestigoByIdDenunciaUsuario.php. Performing a manipulation of the argument id_denuncia results in authorization. This vulnerability is identified as CVE-2025-41338. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in CanalDenuncia.app up to 4.4.7. It has been classified as problematic. This affects an unknown code block of the file /backend/api/buscarTestigoByIdDenunciaUsuario.php. The manipulation of the argument id_denuncia with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality. The summary by CVE is:
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_denuncia' and 'id_user' in '/backend/api/buscarTestigoByIdDenunciaUsuario.php'.
The weakness was released by David Utón Amaya. The advisory is shared at incibe.es. This vulnerability is uniquely identified as CVE-2025-41338 since 04/16/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
By approaching the search of inurl:backend/api/buscarTestigoByIdDenunciaUsuario.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 4.4.8 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: CanalDenuncia.app 4.4.8
Timeline
04/16/2025 CVE reserved11/04/2025 Advisory disclosed
11/04/2025 VulDB entry created
11/04/2025 VulDB entry last update
Sources
Advisory: incibe.esResearcher: David Utón Amaya
Status: Confirmed
CVE: CVE-2025-41338 (🔒)
GCVE (CVE): GCVE-0-2025-41338
GCVE (VulDB): GCVE-100-331161
Entry
Created: 11/04/2025 16:52Changes: 11/04/2025 16:52 (67)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.