CVE-2026-92585 WWBN CVE debrief

Who should care

Defenders and administrators of AVideo installations should assess exposure and verify video access controls to prevent unauthorized access. They should also review and update access permissions for video content, monitor API requests for suspicious activity, and plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

The CVE-2026-92585 vulnerability in AVideo allows logged-in users to vote on restricted videos via the API like endpoint, potentially leading to unauthorized access and data tampering.

• Defenders must verify video access controls to prevent unauthorized access
• Monitoring API requests is necessary to detect suspicious activity
• Reviewing and updating access permissions for video content is required

Technical summary

AVideo through 29.0 fails to validate video access permissions in the API like endpoint, allowing logged-in users to vote on password-protected and group-restricted videos by calling the set.json.php endpoint with APIName parameters. This vulnerability affects AVideo installations and enables attackers to submit like and dislike requests to increment vote counters on videos they cannot watch. Defenders should prioritize verifying video access controls and monitoring API requests to prevent unauthorized access and data tampering.

Defensive priority

Defenders should prioritize verifying video access controls and monitoring API requests to prevent unauthorized access.

Recommended defensive actions

• Verify video access controls and API request validation
• Monitor API requests for suspicious activity
• Review and update access permissions for video content
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but additional information on affected versions and remediation is needed. The vulnerability has been publicly disclosed, and defenders should verify video access controls and monitor API requests to prevent unauthorized access. The CVE Program record and NVD detail page provide source-provided CVE metadata and vulnerability assessment. However, further review of video access controls and API request validation is necessary to ensure the security of AVideo deployments.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.