dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-41358

HIGH · 8.3 CVSS v4.0 Published 2025-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable 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
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'.

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

IDOR vulnerability in CronosWeb's document attachment endpoint allows authenticated users to access other users' documents by manipulating the 'documentCode' parameter. The application fails to validate that the requesting user owns or has permission to access the specified document, enabling unauthorized cross-user document disclosure.

MitigationUpgrade to version 25.00.00.12 or later which should include proper authorization checks. Alternatively, implement server-side validation to verify the authenticated user owns or has permission to access the requested document before serving it.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm CronosWeb installation
    Locate the CronosWeb application in your environment - check web server directories, application pools, or search for 'CronosWeb' in installed programs and configuration files
    Affected if The i2A CronosWeb application is present in your environment
  2. Identify CronosWeb version
    Access the application's version information - typically found in about pages, version info in the UI, configuration files, or assembly/dll metadata if accessible. Compare your installed version against the fixed version 25.00.00.12
    Affected if Installed version is below 25.00.00.12 and you cannot confirm a later patch has been applied
  3. Verify the vulnerable endpoint is accessible
    Check if the URL path '/CronosWeb/Modulos/Personas/DocumentosPersonales/AdjuntarDocumentosPersonas' is routable in your application - examine application routing configuration or attempt to access the endpoint with a valid authenticated session
    Affected if The endpoint responds to requests and accepts the documentCode parameter
  4. Test documentCode parameter authorization
    As an authenticated user, make a request to the vulnerable endpoint using a documentCode value that belongs to a different user. Observe whether the application returns the document without performing ownership or permission validation
    Affected if The application returns documents for documentCodes belonging to other users without authorization checks

You are affected if CronosWeb is present, the version is below 25.00.00.12, and the vulnerable endpoint is accessible without proper document ownership 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 25.00.00.12 or later which should include proper authorization checks. Alternatively, implement server-side validation to verify the authenticated user owns or has permission to access the requested document before serving it.

Recommended fix Moderate confidence

25.00.00.12

  1. 1. Verify the current installed version of i2A CronosWeb by checking the application administration panel or system information.
  2. 2. Download the latest version of CronosWeb (25.00.00.12 or later) from the official i2A vendor distribution channel.
  3. 3. Create a complete backup of the current CronosWeb installation including database and configuration files.
  4. 4. Install version 25.00.00.12 or newer following the vendor's standard upgrade procedure.
  5. 5. After upgrade, verify the fix by attempting to access documents with manipulated documentCode parameters to confirm the authorization check is properly enforced.
  6. 6. Test that legitimate document access still functions correctly for authenticated users within their proper scope.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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