/

CVE-2026-88065

Severity:

HIGH RISK

(7.5)

Broken Access Control (CWE-639) in tts-be API Endpoints

CVE-2026-88065

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-200, CWE-306, CWE-639

Impact:

Sensitive Information Disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

tts-be versions prior to 2.1.0 expose several unauthenticated API endpoints that can be chained to access data from upstream university systems. A remote attacker may use the backend as an open proxy to bypass authorization checks and enumerate or extract student PII, including names, student IDs, schedules, and photos.

Affected context

The vulnerability occurs in tts-be deployments that expose affected API routes without consistently enforcing authentication and object-level authorization. Endpoints involving student photos and course-unit exchange metadata may forward requests to upstream university systems, creating risk when backend trust is applied without verifying the requester's identity and permissions.

Exploit preconditions

  • Attack surface: Internet-accessible tts-be API endpoints
  • Required access: No valid account or prior authentication may be required
  • Trigger point: Requests to affected student and course-unit API routes, potentially chained across endpoints
  • Why exploitation is possible: The backend can act as an open proxy while authorization checks are missing or insufficiently bound to the requested resource

Why this happens

The underlying bug is inconsistent authorization enforcement across API endpoints that handle resources identified by user-controlled values. Requests can reach upstream systems without reliably establishing the caller's identity or verifying access to the requested student or course-unit data.

This maps primarily to CWE-639: Authorization Bypass Through User-Controlled Key, with related characteristics of CWE-306: Missing Authentication for Critical Function and CWE-200: Exposure of Sensitive Information to an Unauthorized Actor. The insecure pattern is trusting route identifiers or backend placement as a substitute for explicit authentication and object-level authorization.

Potential impact

  • An attacker may enumerate student records and course-related metadata
  • Sensitive PII, including full names and student IDs, could be disclosed
  • Class schedules and student photos may be extracted without authorization
  • Upstream university systems could be used as an unintended data-access proxy
  • The incident could increase privacy, compliance, and reputational risk

General mitigation guidance

Mitigation generally focuses on enforcing authentication and authorization consistently at every sensitive API boundary.

Common defensive patterns include:

  • Require authentication before processing requests for student or course-unit resources
  • Enforce object-level authorization using the authenticated user's roles and permitted scope
  • Avoid treating route identifiers, internal network location, or upstream trust as authorization evidence
  • Restrict proxy behavior to explicitly allowed operations and resource scopes
  • Minimize returned fields and apply data-access policies to sensitive PII
  • Use least-privilege service accounts when accessing upstream university systems
  • Apply secure-by-default denial for missing, invalid, or ambiguous authorization context

How teams detect issues like this

Organizations can detect similar issues through:

  • Static analysis and API security checks for routes lacking authentication or authorization middleware
  • Code review searches for direct use of path identifiers in upstream requests without ownership checks
  • Tests that attempt cross-user and unauthenticated access to resource endpoints
  • API gateway policies requiring authentication and approved scopes for sensitive routes
  • Monitoring for unusual enumeration patterns, sequential identifiers, high-volume photo retrieval, and requests lacking expected identity context
  • Automated security review tools that identify missing authentication and object-level authorization controls

Sources

SourceLink
github.comgithub.com/NIAEFEUP/tts-be/security/advisories/GHSA-fpfp-hr42-fvpm

Frequently asked

questions

Yes. Where affected endpoints are reachable over the network and do not require authentication, a remote attacker may submit requests directly and chain endpoint behavior.

No legitimate account may be necessary. Network access to the exposed tts-be API is the key prerequisite, although deployment controls may limit exposure.

Require authentication and perform explicit, server-side object-level authorization before forwarding or fulfilling every sensitive request.

Use deny-by-default API policies, centralized authorization middleware, least-privilege upstream credentials, and automated tests covering unauthenticated and cross-user resource access.

Find out what's already
exploitable in your codebase.