Description
Inadequate access control in Hiperdino’s REST v1.0 API. The public endpoint ‘customer/check’ could allow an authenticated attacker to enter a telephone number or an email address. When the value entered belongs to a registered customer, the service returns the associated information (email address and telephone number). No authentication is required beyond a static bearer token, and there is no rate limiting or generic error handling. Successful exploitation of this vulnerability could allow a remote attacker to enumerate a user’s contact details, although this would require obtaining a valid static bearer token, constituting an information disclosure vulnerability.
Published: 2026-09-14
Score: 9.2 Critical
EPSS: n/a
KEV: No
Impact: Information Disclosure
Action: Restrict Access
AI Analysis

Impact

Hiperdino’s REST API v1.0 exposes a public endpoint called /customer/check that permits an authenticated user to supply a telephone number or an email address. If the supplied value belongs to a registered customer, the service returns that customer’s email and telephone number. The only authentication required is a static bearer token, and there is no rate limiting or generic error handling. Thus the flaw is an access‑control weakness that allows an adversary who possesses a valid bearer token to enumerate contact details of existing users, constituting an information‑disclosure vulnerability.

Affected Systems

Hiperdino REST API, version 1.0.

Risk and Exploitability

The CVSS score of 9.2 classifies this flaw as critical. Because the API is publicly reachable over the network and requires only a static bearer token, the attack vector is remote. Although the attacker must first obtain a valid bearer token to exploit the vulnerability, once that prerequisite is met, enumeration is trivial and no further privileges are needed. The EPSS score is unavailable and the vulnerability is not listed in CISA’s KEV catalog, yet the high CVSS and the lack of mitigation make the risk significant.

Generated by OpenCVE AI on September 14, 2026 at 20:14 UTC.

Remediation

Vendor Solution

No solution has been reported as yet.


OpenCVE Recommended Actions

  • Limit access to the customer/check endpoint by implementing role‑based authorization or removing the endpoint entirely
  • Enforce stronger authentication such that the bearer token is associated with a user account and session, adding minimum necessary privileges
  • Enable rate limiting and implement generic error responses to prevent automated enumeration

Generated by OpenCVE AI on September 14, 2026 at 20:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 14 Sep 2026 21:00:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Mon, 14 Sep 2026 12:30:00 +0000

Type Values Removed Values Added
Description Inadequate access control in Hiperdino’s REST v1.0 API. The public endpoint ‘customer/check’ could allow an authenticated attacker to enter a telephone number or an email address. When the value entered belongs to a registered customer, the service returns the associated information (email address and telephone number). No authentication is required beyond a static bearer token, and there is no rate limiting or generic error handling. Successful exploitation of this vulnerability could allow a remote attacker to enumerate a user’s contact details, although this would require obtaining a valid static bearer token, constituting an information disclosure vulnerability.
Title Inadequate access control in the Hiperdino REST API
First Time appeared Hiperdino
Hiperdino rest Api
Weaknesses CWE-284
CPEs cpe:2.3:a:hiperdino:rest_api:1.0:*:*:*:*:*:*:*
Vendors & Products Hiperdino
Hiperdino rest Api
References
Metrics cvssV4_0

{'score': 9.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N'}


Subscriptions

Hiperdino Rest Api
cve-icon MITRE

Status: PUBLISHED

Assigner: INCIBE

Published:

Updated: 2026-09-14T14:18:26.668Z

Reserved: 2026-06-15T09:37:00.376Z

Link: CVE-2026-12258

cve-icon Vulnrichment

Updated: 2026-09-14T14:18:20.076Z

cve-icon NVD

Status : Received

Published: 2026-09-14T13:17:33.290

Modified: 2026-09-14T15:17:04.153

Link: CVE-2026-12258

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-14T20:15:06Z

Weaknesses