CVE-2025-3575
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 · uneditedInsecure Direct Object Reference vulnerability in Deporsite from T-INNOVA allows an attacker to retrieve sensitive information from others users via "idUsuario" parameter in "/helper/Familia/establecerUsuarioSeleccion" endpoint.
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 Deporsite from T-INNOVA. The application fails to properly validate that the authenticated user has authorization to access the requested user data before processing the 'idUsuario' parameter in the /helper/Familia/establecerUsuarioSeleccion endpoint, allowing any authenticated user to retrieve sensitive information from other users by manipulating this parameter.
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
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Deporsite installationIdentify the installed application as Deporsite from T-INNOVA by checking the application name, banner, or configuration files that reference T-INNOVA or DeporsiteAffected if The application is Deporsite from T-INNOVA and the /helper/Familia/establecerUsuarioSeleccion endpoint exists and accepts the idUsuario parameter
-
Locate the vulnerable endpointCheck if the endpoint /helper/Familia/establecerUsuarioSeleccion is accessible in the application by inspecting web server routes, proxy configurations, or by attempting to access the URL path directlyAffected if The endpoint exists and is reachable without additional access controls beyond authentication
-
Verify authentication is requiredConfirm that the endpoint requires a valid user session by attempting to access it without authentication - a request without a valid session should be rejected with an authentication errorAffected if The endpoint requires authentication but does not perform authorization checks on the idUsuario parameter
-
Test IDOR vulnerability with idUsuario parameterLog in as a low-privilege or standard authenticated user, then send a request to the endpoint with a manipulated idUsuario parameter pointing to a different user's ID - observe if the application returns that other user's sensitive information without authorization verificationAffected if Manipulating the idUsuario parameter to another user's ID returns that user's data despite the requesting user not having permission to access it
-
Check authorization logic in application codeReview the server-side code handling the /helper/Familia/establecerUsuarioSeleccion endpoint to confirm there is no validation that the authenticated user owns or has permission to access the idUsuario being requestedAffected if The code processes the idUsuario parameter without verifying the authenticated user has rights to access that specific user record
A user is affected if they have Deporsite from T-INNOVA running with the /helper/Familia/establecerUsuarioSeleccion endpoint accessible and the application allows any authenticated user to retrieve data from other user accounts by manipulating the idUsuario parameter.
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.
From vendor dataImplement proper authorization checks to verify the requesting user has permission to access the specified user data. Additionally, use indirect references (mapping internal IDs to external references) and validate user session/context before returning any user-specific data.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3575 — 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-3575 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