CVE-2026-6008: Im Park Information Technology, Electronics, Press, Publishing and Advertising, Education Ltd. Co DijiDemi · Insecure Direct Object Reference
Affects Im Park Information Technology, Electronics, Press, Publishing and Advertising, Education Ltd. Co DijiDemiSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium : upgrade to v4.5.13.0 when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in v4.5.13.0
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade Im Park Information Technology, Electronics, Press, Publishing and Advertising, Education Ltd. Co DijiDemi to v4.5.13.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Im Park Information Technology, Electronics, Press, Publishing and Advertising, Education Ltd. Co.DijiDemi | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, organizations should carefully review and restrict user privileges to minimize potential abuse. Monitor for unusual privilege escalations or unauthorized actions by users with high privileges.
Description
Authorization bypass through User-Controlled key vulnerability in Im Park Information Technology, Electronics, Press, Publishing and Advertising, Education Ltd. Co. DijiDemi allows Privilege Abuse. This issue affects DijiDemi: from v4.5.12.1 before v4.5.13.0.