Unauthorized record access via user-controlled identifiers
Published Jul 21, 2025 · Updated Jun 6, 2026
Authorization bypass in Turtek Software Eyotek before 11.03.2025 allows remote attackers to read other users' records via crafted identifiers. The published record does not identify the affected request, parameter, or code path; it states only that Eyotek trusts a user-controlled key without enforcing authorization. No authentication or user interaction is required, and successful exploitation exposes data without reported modification or service interruption.
Summary
What happened
Authorization bypass in Turtek Software Eyotek before 11.03.2025 allows remote attackers to read other users' records via crafted identifiers. The published record does not identify the affected request, parameter, or code path; it states only that Eyotek trusts a user-controlled key without enforcing authorization. No authentication or user interaction is required, and successful exploitation exposes data without reported modification or service interruption.
The record
- CVE
- CVE-2025-1469
- Published
- Jul 21, 2025
- Updated
- Jun 6, 2026
- Vendor
- TURTEK Yazılım Tic. Ltd. Şti.
- Product
- Eyotek
- Classifications
- CWE-639, CAPEC-21, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 2025CVE publishedPublication date reported by the CVE source.
- Jun 6, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <11.03.2025
What conditions does exploitation require?
What is affected?
Published CVSS scores
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