Skip to main content
VulnerabilityPublished

CVE-2026-23487: blinkospace blinko · Insecure Direct Object Reference

Affects blinkospace blinkoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 Medium : upgrade to 1.8.4 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.8.4
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade blinko and blinkospace/blinko to 1.8.4.

Affected software

ProductAffectedFixed in
blinkospaceblinkoAffected
  • <1.8.4
Fixed in
  • 1.8.4
GitHubblinkospace/blinkopkg:github/blinkospace/blinkoOther threatsAffected
  • <1.8.4
Fixed in
  • 1.8.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade Blinko to version 1.8.4 or later to ensure the authorization bypass vulnerability is patched. Until the upgrade is applied, restrict access to the user.detail endpoint through network segmentation and strict access control lists to limit exposure. Implement monitoring and alerting for unusual access patterns to the user.detail API, especially requests originating from accounts with low privileges. Conduct a thorough audit of superadmin token usage and rotate tokens if there is any suspicion of compromise. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious API calls targeting the user.detail endpoint. Additionally, review and strengthen authorization logic across all API endpoints to prevent similar IDOR vulnerabilities. Educate developers on secure coding practices related to access control and object references to avoid recurrence. Finally, maintain an incident response plan to quickly address any exploitation attempts.

Description

Blinko is an AI-powered card note-taking project. Prior to version 1.8.4, there is an IDOR vulnerability where user.detail Endpoint Leaks the Superadmin Token. This issue has been patched in version 1.8.4.

References

Community reviews

Loading reviews…