Account takeover via credentialed origin reflection
Published Apr 21, 2026 · Updated Apr 21, 2026
Cross-origin policy failure in AVideo 29.0 and earlier allows remote attackers to read or modify authenticated API data. The allowOrigin(true) path in objects/functions.php reflects an arbitrary Origin while enabling credentials for the get.json.php and set.json.php API endpoints. Exploitation requires a logged-in user to visit an attacker-controlled page; the page can read PII and livestream secrets or submit state-changing API requests.
Summary
What happened
Cross-origin policy failure in AVideo 29.0 and earlier allows remote attackers to read or modify authenticated API data. The allowOrigin(true) path in objects/functions.php reflects an arbitrary Origin while enabling credentials for the get.json.php and set.json.php API endpoints. Exploitation requires a logged-in user to visit an attacker-controlled page; the page can read PII and livestream secrets or submit state-changing API requests.
The record
- CVE
- CVE-2026-41056
- Published
- Apr 21, 2026
- Updated
- Apr 21, 2026
- Vendor
- World Wide Broadcast Network
- Product
- AVideo
- Classifications
- CWE-942, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2026CVE publishedPublication date reported by the CVE source.
- Apr 21, 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=<= 29.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- GitHub advisory credentialed CORS proof of conceptproof of concept · unverified
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