Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-33685: CWE-862: Missing Authorization in WWBN AVideo

0
Medium
VulnerabilityCVE-2026-33685cvecve-2026-33685cwe-862
Published: Mon Mar 23 2026 (03/23/2026, 18:42:45 UTC)
Source: CVE Database V5
Vendor/Project: WWBN
Product: AVideo

Description

CVE-2026-33685 is a medium severity vulnerability in WWBN AVideo versions up to 26. 0 where the JSON API endpoint for ad campaign reports lacks any authentication or authorization checks. This allows unauthenticated attackers to access sensitive ad analytics data including video titles, user channel names, user IDs, ad campaign names, and impression/click counts. While the HTML and CSV report endpoints enforce admin checks, the JSON endpoint was left unprotected. The vulnerability does not allow modification of data or system compromise but leaks confidential business and user information. A patch has been committed to fix this missing authorization issue. Organizations using affected versions should update promptly to prevent unauthorized data disclosure.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/30/2026, 20:37:21 UTC

Technical Analysis

WWBN AVideo is an open source video platform widely used for hosting and managing video content. In versions up to and including 26.0, the endpoint `plugin/AD_Server/reports.json.php` exposes ad campaign analytics data without any authentication or authorization controls. This endpoint returns sensitive information such as video titles, user channel names, user IDs, ad campaign names, and impression and click counts. The vulnerability arises because the JSON API endpoint was not protected by the `User::isAdmin()` check that is correctly enforced on the HTML (`reports.php`) and CSV export (`getCSV.php`) counterparts. This missing authorization (CWE-862) allows any unauthenticated attacker to retrieve detailed advertising analytics data, which could be used for competitive intelligence, user profiling, or targeted attacks. The issue was identified and a patch was committed (commit daca4ffb1ce19643eecaa044362c41ac2ce45dde) to enforce proper admin authorization on the JSON endpoint. The CVSS v3.1 score is 5.3 (medium severity), reflecting the ease of exploitation (no authentication or user interaction required) but limited impact to confidentiality only, with no integrity or availability impact. No known exploits in the wild have been reported yet.

Potential Impact

The primary impact of this vulnerability is unauthorized disclosure of sensitive advertising analytics data. Organizations using affected versions of WWBN AVideo risk leakage of business intelligence such as ad campaign performance metrics, user channel information, and video metadata. This information could be leveraged by competitors or malicious actors for profiling, reconnaissance, or crafting targeted social engineering attacks. Although the vulnerability does not allow modification or disruption of services, the confidentiality breach can undermine user trust and violate privacy policies or contractual obligations. For organizations relying on AVideo for monetization or user engagement analytics, this data exposure could result in financial and reputational damage. Since exploitation requires no authentication and no user interaction, the attack surface is broad, increasing the likelihood of opportunistic data harvesting.

Mitigation Recommendations

Organizations should immediately upgrade to a patched version of WWBN AVideo that includes the fix for this vulnerability. If upgrading is not immediately possible, administrators should implement access controls at the web server or network level to restrict access to the `plugin/AD_Server/reports.json.php` endpoint to trusted administrative IP addresses only. Additionally, auditing and monitoring access logs for unusual or unauthorized requests to this endpoint can help detect exploitation attempts. Developers maintaining custom forks or deployments should verify that all API endpoints enforce consistent authorization checks, especially for administrative data. Regular security reviews and automated testing for missing authorization vulnerabilities (CWE-862) should be integrated into the development lifecycle to prevent similar issues. Finally, organizations should review their data exposure policies and ensure that sensitive analytics data is only accessible to authorized personnel.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-23T16:34:59.931Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69c18de6f4197a8e3b82dd8d

Added to database: 3/23/2026, 7:00:54 PM

Last enriched: 3/30/2026, 8:37:21 PM

Last updated: 5/7/2026, 4:34:10 AM

Views: 58

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses