Cross-Site Request Forgery in AVideo Release Endpoint

WWBN AVideo through commit 9c39d8c8 contains a cross-site request forgery vulnerability in the releaseVideoNow.json.php endpoint that lacks authenticity checks and accepts GET requests. Attackers can craft a malicious cross-site GET request carrying an administrator's session cookie to permanently publish any embargoed video by manipulating the videos_id parameter.

Casky was already ahead

This CVE exploits attack patterns that Casky's 322matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

WWBN AVideo contains a critical cross-site request forgery (CSRF) vulnerability in its releaseVideoNow.json.php endpoint that allows attackers to permanently publish embargoed videos without authorization. The vulnerability stems from missing authenticity checks and improper acceptance of GET requests—a dangerous combination that violates secure API design principles. Attackers can exploit administrator session cookies through malicious cross-site requests to manipulate the videos_id parameter and release restricted content. This affects any organization running vulnerable versions of AVideo, particularly those managing sensitive or time-sensitive video content, compliance-restricted materials, or embargoed announcements. The high CVSS score of 7.1 reflects the significant integrity and confidentiality impact of unauthorized content release.

Casky's Claude-powered analysis engine maps this vulnerability to MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance), identifying how attackers probe for session-based trust relationships and craft social engineering vectors to trigger unauthorized actions. Across 322 matched security skills, practitioners would observe detection patterns flagging suspicious cross-origin POST/GET requests to sensitive endpoints, anomalous session usage from unexpected referrer sources, and GET requests to JSON endpoints that should only accept POST with CSRF tokens. The extended reasoning capability would connect these signals to reveal the attack chain: session hijacking through CSRF → privilege escalation through administrative action → data integrity violation. Security teams would see findings highlighting missing CSRF token validation, improper HTTP method restrictions, and insufficient request origin verification—actionable insights enabling immediate remediation.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

322 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-58003.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-58003

Casky has 322 skills that investigate the attack patterns behind CVE-2026-58003. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn