CVE-2025-41030
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 · uneditedLack of authorisation in Deporsite by T-INNOVA. This vulnerability allows an unauthenticated attacker to obtain information from other users via GET ‘/ajax/TInnova_v2/Integrantes_Recurso_v2_1/llamadaAjax/buscarPersona’ using the ‘dni’ parameter.
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 confidenceAn authorization bypass in Deporsite allows unauthenticated attackers to query a user lookup endpoint (GET /ajax/TInnova_v2/Integrantes_Recurso_v2_1/llamadaAjax/buscarPersona) using the 'dni' parameter to retrieve personally identifiable information (national ID numbers) of other users. This is a broken access control/IDOR vulnerability where no authentication or ownership validation is performed before returning sensitive personal data.
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:L/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 Deporsite installation and versionCheck the application files, configuration, or admin panel for the installed Deporsite version number. Compare against any available version documentation to determine if the installation predates the CVE fix.Affected if The installed version is older than the patched version and the vulnerable endpoint is accessible.
-
Verify the vulnerable endpoint existsAttempt to access the path /ajax/TInnova_v2/Integrantes_Recurso_v2_1/llamadaAjax/buscarPersona via HTTP GET request. This can be done with a browser, curl, or similar tool.Affected if The endpoint returns any HTTP response (200, 401, 403, etc.) indicating the path exists and is reachable.
-
Test endpoint authentication requirementSend a GET request to the vulnerable endpoint with a 'dni' parameter (e.g., ?dni=12345678) without providing any session token, cookie, or authentication credentials. Observe the HTTP response code and behavior.Affected if The request succeeds with a 200 OK response and returns data without requiring any authentication.
-
Verify authorization bypass on DNI lookupWith no authentication, request different DNI values (different from your own user account if authenticated access exists) and confirm whether the endpoint returns other users' national ID numbers or PII.Affected if The endpoint returns national ID numbers or other PII for arbitrary DNI values without validating user ownership or session context.
You are affected if Deporsite is installed and the /buscarPersona endpoint is reachable without authentication, returning other users' national ID numbers.
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 authentication enforcement and authorization checks on the affected endpoint to ensure users can only access their own data. Validate that the requesting user is authenticated and authorized to retrieve the requested DNI information.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41030 — 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-41030 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