A critical path traversal vulnerability in Blinko versions prior to 1.8.4 permits unauthenticated attackers to exfiltrate sensitive data, including user notes and authentication tokens.

The vulnerability exists in the file server endpoint, which fails to perform adequate permission checks or path sanitization on the temp/ directory. This allows an unauthenticated attacker to bypass directory restrictions and access arbitrary files on the host system.

The ability for an attacker to read arbitrary files, specifically backup files containing all user notes and authentication tokens, poses a severe risk to data confidentiality. With access to user tokens, an attacker could escalate their access to impersonate legitimate users and gain full control over private information. Given the CVSS score of 7.5, this high-severity flaw requires immediate attention to prevent significant data breaches and potential regulatory non-compliance.

Immediate Action: Update the Blinko application to version 1.8.4 or later immediately to apply the necessary path filtering and permission checks.

Proactive Monitoring: Review server access logs for anomalous requests targeting the temp/ directory or patterns indicative of directory traversal attempts.

Compensating Controls: Implement a Web Application Firewall (WAF) rule to block requests containing path traversal sequences (such as dot-dot-slash patterns) directed at the file server endpoint.

Public Exploit Available: No (A Nuclei detection template exists, but no weaponized exploit or public proof-of-concept has been identified.)

This vulnerability represents a significant security oversight that exposes sensitive user data to unauthorized parties. Organizations currently running Blinko should prioritize the upgrade to version 1.8.4 as their primary security objective. Failure to patch this issue could lead to complete compromise of sensitive user information and long-term reputational damage.