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.
Published: 2026-10-14
Score: 8.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Account takeover via cleartext password exposure
Action: Patch ASAP
AI Analysis

Impact

ServiceNext’s /api/Usuario/GetUsuarios endpoint allows an authenticated user to supply a numeric ID in the request body without confirming that the token belongs to the requested account, creating an IDOR flaw (CWE‑639). The flaw lets any authenticated user enumerate user IDs and retrieve the full profile of every other user, including passwords stored in cleartext (CWE‑256). This exposure enables immediate account takeover and credential‑stuffing attacks.

Affected Systems

ServiceNext by SerTec is affected. No version information is disclosed in the advisory.

Risk and Exploitability

With a CVSS score of 8.1 the vulnerability is considered high severity. The EPSS score is not provided, and the vulnerability is not listed in CISA KEV. Attackers need only an authenticated token; iterating numeric IDs is trivial, so exploitation likelihood is high if the service is publicly accessible. The impact is full access to other users’ cleartext passwords, making exploitation potentially catastrophic.

Generated by OpenCVE AI on October 15, 2026 at 14:18 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor‑released patch that removes the IDOR by enforcing token‑to‑account validation.
  • If a patch is unavailable, modify the endpoint to check that the ID in the request body matches the user identifier in the authenticated token or deny the request.
  • Update the password storage mechanism to hash passwords using a secure algorithm such as bcrypt, Argon2, or PBKDF2, eliminating cleartext credentials.

Generated by OpenCVE AI on October 15, 2026 at 14:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 19 Oct 2026 13:30:00 +0000

Type Values Removed Values Added
First Time appeared Servicenext
Servicenext sertec
Vendors & Products Servicenext
Servicenext sertec

Fri, 16 Oct 2026 21:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


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

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}


Subscriptions

Servicenext Sertec
cve-icon MITRE

Status: PUBLISHED

Assigner: BLSOPS

Published:

Updated: 2026-10-16T20:15:51.180Z

Reserved: 2026-09-10T00:45:43.207Z

Link: CVE-2026-79957

cve-icon Vulnrichment

Updated: 2026-10-16T20:15:40.902Z

cve-icon NVD

Status : Deferred

Published: 2026-10-14T18:18:19.133

Modified: 2026-10-16T21:19:53.860

Link: CVE-2026-79957

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-19T13:07:37Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key