Contact-data disclosure via static-token customer enumeration
Published Sep 14, 2026 · Updated Sep 14, 2026
Access control failure in Hiperdino REST API v1.0 allows remote authenticated users to enumerate customer contact details. The public customer/check endpoint accepts an email address or telephone number and returns both fields for a registered customer without account-specific authorization. A valid static bearer token is required, but the absence of rate limiting and generic errors enables bulk discovery of registered customers' email addresses and telephone numbers.
Summary
What happened
Access control failure in Hiperdino REST API v1.0 allows remote authenticated users to enumerate customer contact details. The public customer/check endpoint accepts an email address or telephone number and returns both fields for a registered customer without account-specific authorization. A valid static bearer token is required, but the absence of rate limiting and generic errors enables bulk discovery of registered customers' email addresses and telephone numbers.
The record
- CVE
- CVE-2026-12258
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1589
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo