Account data exposure via user-controlled authorization key
Published Mar 5, 2025 · Updated Jun 2, 2026
Authorization bypass in PİK Online before 3.1.5 allows remote authenticated users to access private account data via a user-controlled key. The public record identifies the key as the authorization locus but does not disclose the affected request, field, or omitted server-side check. A valid low-privilege account is required; successful access supports account footprinting and session hijacking, while the exposed data and session artifact remain undisclosed.
Summary
What happened
Authorization bypass in PİK Online before 3.1.5 allows remote authenticated users to access private account data via a user-controlled key. The public record identifies the key as the authorization locus but does not disclose the affected request, field, or omitted server-side check. A valid low-privilege account is required; successful access supports account footprinting and session hijacking, while the exposed data and session artifact remain undisclosed.
The record
- CVE
- CVE-2024-11216
- Published
- Mar 5, 2025
- Updated
- Jun 2, 2026
- Vendor
- Pik Online Yazılım Çözümleri A.Ş.
- Product
- PİK Online
- Classifications
- CWE-359, CWE-639, CAPEC-593, CAPEC-575
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 5, 2025CVE publishedPublication date reported by the CVE source.
- Jun 2, 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 <3.1.5
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