Authenticated comment injection via unchecked videoId authorization
Published Aug 11, 2026 · Updated Aug 11, 2026
Broken access control in Cap 0.3.1 allows remote authenticated users to inject comments into private videos through the comment API. The POST /api/video/comment handler authenticates the session but inserts a caller-supplied videoId without checking view or interaction permission. A valid account and a guessed video ID are required; successful requests store attacker-authored comments, trigger owner email notifications, and disclose valid IDs through response differences.
Summary
What happened
Broken access control in Cap 0.3.1 allows remote authenticated users to inject comments into private videos through the comment API. The POST /api/video/comment handler authenticates the session but inserts a caller-supplied videoId without checking view or interaction permission. A valid account and a guessed video ID are required; successful requests store attacker-authored comments, trigger owner email notifications, and disclose valid IDs through response differences.
The record
- CVE
- CVE-2026-69113
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Cap Software, Inc.
- Product
- Cap
- Classifications
- CWE-862, T1565.001, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 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=0 <=0.3.1
What conditions does exploitation require?
What is affected?
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
- Authenticated comment-injection proof of conceptproof of concept · demonstrated
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