CVE-2025-41358
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-10

Last updated on: 2025-12-10

Assigner: Spanish National Cybersecurity Institute, S.A. (INCIBE)

Description
Direct Object Reference Vulnerability (IDOR) in i2A's CronosWeb, in versions prior to 25.00.00.12, inclusive. This vulnerability could allow an authenticated attacker to access other users' documents by manipulating the ‘documentCode’ parameter in '/CronosWeb/Modulos/Personas/DocumentosPersonales/AdjuntarDocumentosPersonas'.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-10
Last Modified
2025-12-10
Generated
2026-06-16
AI Q&A
2025-12-10
EPSS Evaluated
2026-06-15
NVD
CVE-2025-41358
EUVD
EUVD-2025-202413
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
i2a cronosweb 25.00
i2a cronosweb 24.05
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2025-41358 is a Direct Object Reference (IDOR) vulnerability in CronosWeb by i2A, affecting versions prior to 25.00.00.12. It allows an authenticated attacker to access other users' documents by manipulating the 'documentCode' parameter in a specific endpoint. This means that by changing this parameter, an attacker can view documents they should not have access to. [1]

Impact Analysis

This vulnerability can impact you by allowing an authenticated attacker to access sensitive documents belonging to other users without authorization. This could lead to unauthorized disclosure of personal or confidential information managed within the CronosWeb platform. [1]

Detection Guidance

This vulnerability can be detected by monitoring requests to the endpoint '/CronosWeb/Modulos/Personas/DocumentosPersonales/AdjuntarDocumentosPersonas' and checking for manipulation of the 'documentCode' parameter. You can use network traffic analysis tools like curl or wget to send authenticated requests with different 'documentCode' values to see if unauthorized documents are accessible. For example, using curl: curl -X GET 'https://<your-cronosweb-domain>/CronosWeb/Modulos/Personas/DocumentosPersonales/AdjuntarDocumentosPersonas?documentCode=<value>' -H 'Cookie: <authenticated-session-cookie>' and observe if documents of other users are returned. [1]

Mitigation Strategies

The immediate mitigation step is to upgrade CronosWeb to version 25.01 or later, where this vulnerability has been fixed. Additionally, restrict access to the affected endpoint to only authorized users and monitor for suspicious activity involving the 'documentCode' parameter. [1]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-41358. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart