CVE-2026-58003
Received Received - Intake

CSRF in AVideo via Release Video Endpoint

Vulnerability report for CVE-2026-58003, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-22

Last updated on: 2026-08-22

Assigner: VulnCheck

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-22
Last Modified
2026-08-22
Generated
2026-08-22
AI Q&A
2026-08-22
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
wwbn avideo From 9c39d8c8 (inc)
wwbn avideo to 9c39d8c8 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-58003 is a Cross-Site Request Forgery (CSRF) vulnerability in WWBN AVideo software. It exists in the releaseVideoNow.json.php endpoint which lacks authenticity checks and accepts GET requests. Attackers can trick an administrator into visiting a malicious link or loading a malicious image to force-publish any embargoed video by manipulating the videos_id parameter. The vulnerability allows permanent disclosure of embargoed videos as the scheduler marks the video as executed.

Detection Guidance

To detect this vulnerability, inspect the AVideo application for the presence of the releaseVideoNow.json.php endpoint in the plugin/Scheduler directory. Check if the endpoint accepts GET requests and lacks CSRF token validation. Review server logs for suspicious GET requests targeting this endpoint with parameters like videos_id.

Impact Analysis

If you use WWBN AVideo, an attacker could exploit this to publish videos you intended to keep private. This could lead to unauthorized disclosure of sensitive or embargoed content. The attack requires tricking an authenticated administrator into interacting with a malicious request, but does not require the attacker to have an account.

Compliance Impact

This vulnerability could lead to unauthorized disclosure of sensitive data, which may violate compliance requirements under GDPR (data protection) or HIPAA (health information privacy). Unauthorized publication of embargoed videos could result in data breaches, leading to regulatory penalties, reputational damage, and loss of trust.

Mitigation Strategies

Immediately update AVideo to the latest version that includes CSRF protection. Add CSRF token checks to the releaseVideoNow.json.php endpoint and ensure it rejects GET requests. Implement input validation for the videos_id parameter and restrict access to the endpoint to authenticated administrators only.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-58003. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart