Privilege abuse via user-controlled key
Published May 14, 2026 · Updated May 14, 2026
Authorization bypass in DijiDemi 4.5.12.1 before 4.5.13.0 allows remote authenticated users to abuse privileges via a user-controlled key. The published record does not identify the affected endpoint, object key, or authorization check, so the concrete lookup and missing entitlement validation remain undisclosed. Exploitation requires high-privileged access and user interaction; the record reports privilege abuse but does not identify the data or operations exposed.
Summary
What happened
Authorization bypass in DijiDemi 4.5.12.1 before 4.5.13.0 allows remote authenticated users to abuse privileges via a user-controlled key. The published record does not identify the affected endpoint, object key, or authorization check, so the concrete lookup and missing entitlement validation remain undisclosed. Exploitation requires high-privileged access and user interaction; the record reports privilege abuse but does not identify the data or operations exposed.
The record
- CVE
- CVE-2026-6008
- Published
- May 14, 2026
- Updated
- May 14, 2026
- Vendor
- İM Park Eğitim Bilişim
- Product
- DijiDemi
- Classifications
- CWE-639
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2026CVE publishedPublication date reported by the CVE source.
- May 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=v4.5.12.1 <v4.5.13.0
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