ServiceNext contains an insecure direct object reference (IDOR) in the /api/Usuario/GetUsuarios endpoint, which accepts a user-controlled numeric ID in the request body without verifying that the authenticated token belongs to the requested account (CWE-639). Any authenticated user can iterate the ID parameter to retrieve the full profile record of every other user, including passwords stored in cleartext (CWE-256), enabling account takeover and credential-stuffing attacks.
Project Subscriptions
No data.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Wed, 14 Oct 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | ServiceNext contains an insecure direct object reference (IDOR) in the /api/Usuario/GetUsuarios endpoint, which accepts a user-controlled numeric ID in the request body without verifying that the authenticated token belongs to the requested account (CWE-639). Any authenticated user can iterate the ID parameter to retrieve the full profile record of every other user, including passwords stored in cleartext (CWE-256), enabling account takeover and credential-stuffing attacks. | |
| Title | ServiceNext Insecure Direct Object Reference via GetUsarios | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: BLSOPS
Published:
Updated: 2026-10-14T18:01:51.493Z
Reserved: 2026-09-10T00:45:43.207Z
Link: CVE-2026-79957
No data.
Status : Received
Published: 2026-10-14T18:18:19.133
Modified: 2026-10-14T18:18:19.133
Link: CVE-2026-79957
No data.
OpenCVE Enrichment
No data.
Weaknesses