CVE-2025-3574
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/obtenerFamiliaUsuario" 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 confidenceIDOR vulnerability in Deporsite's /helper/Familia/obtenerFamiliaUsuario endpoint allows unauthenticated or authenticated users to retrieve other users' family data by manipulating the idUsuario parameter. This is a horizontal privilege escalation where users can access data belonging to other users at the same privilege level.
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.
-
Identify if the vulnerable endpoint is exposedScan your web application's URL paths for /helper/Familia/obtenerFamiliaUsuario or examine web server access logs for requests to this endpointAffected if The endpoint exists and is reachable via HTTP/HTTPS requests
-
Verify if the idUsuario parameter is acceptedSend a GET or POST request to /helper/Familia/obtenerFamiliaUsuario with an idUsuario parameter value and observe the responseAffected if The application accepts and processes the idUsuario parameter without rejecting it
-
Test for unauthorized data accessWith an authenticated session, submit two requests with different idUsuario values (e.g., idUsuario=1 and idUsuario=2) and compare if each returns different users' family dataAffected if Different idUsuario values return different users' family information without proper authorization validation
-
Confirm endpoint accessibilityAttempt to access the endpoint without any authentication credentials (anonymous request)Affected if The endpoint returns family data or valid error responses to unauthenticated requests, indicating it lacks proper access controls
-
Check for authorization logic in application codeReview the server-side code handling /helper/Familia/obtenerFamiliaUsuario to verify if it validates that the requesting user owns or has permission to access the idUsuario being requestedAffected if No code exists that compares the authenticated user's ID against the requested idUsuario before returning data
Your environment is affected if the /helper/Familia/obtenerFamiliaUsuario endpoint is accessible and allows manipulation of the idUsuario parameter to retrieve family data belonging to other users without proper authorization validation.
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 validating that the requesting user has permission to access the requested user data, and consider replacing direct object references with indirect references (e.g., mapping internal IDs to random/encrypted values).
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3574 — 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-3574 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