Technical impact
The flaw in MyTube occurs when the backend lacks enforcement of the visitor role’s visibility restrictions. When a site enables visitor authentication and assigns a visitor password, the API endpoints `/api/videos` and `/api/videos/:id` return all video records, including those marked with `visibility=0`. This exposes hidden metadata such as titles, source URLs, video file paths, subtitle paths, and thumbnails. Visitors can also download media files through the `serveMountVideo` route or unprotected `/videos/*` and `/subtitles/*` paths, effectively granting full media access without credentials. The vulnerability stems from missing authentication checks at the API and file‑serving layers, mapping to a significant loss of confidentiality for content owners and potential abuse by unauthenticated users.
Affected Systems
The flaw impacts installations of Franklioxygen's MyTube application running any version earlier than 1.10.3. The issue manifests when the configuration sets `loginEnabled=true` and a visitor password is defined, allowing visitor accounts to bypass intended read‑only access. Deployments that retain the default setting of `loginEnabled=false`, such as single‑user or owner‑equivalent setups, are not affected because all callers possess owner privileges. Updating to 1.10.3 removes the unrestricted visibility checks and corrects the backend endpoint behavior.
Risk and Exploitability
The CVSS score of 7.1 places this weakness in the high‑to‑critical range, and although EPSS data is not available, the lack of authentication checks makes exploitation straightforward for anyone who can reach the API. The vulnerability is not listed in the CISA KEV catalog, yet the public nature of the affected endpoints and the permissive visitor settings mean attackers can enumerate video resources without privileged credentials. The available paths to obtain media files risk unlicensed distribution and intellectual property exposure if the content is proprietary.