LiveActive security incident?Get immediate response
CVE Record

CVE-2026-33237: AVideo has SSRF in Scheduler Plugin via callbackURL Missing `isSSRFSafeURL()` Validation

WWBN AVideo is an open source video platform. Prior to version 26.0, the Scheduler plugin's `run()` function in `plugin/Scheduler/Scheduler.php` calls `url_get_contents()` with an admin-configurable `callbackURL` that is validated only by `isValidURL()` (URL format check). Unlike other AVideo endpoints that were recently patched for SSRF (GHSA-9x67-f2v7-63rw, GHSA-h39h-7cvg-q7j6), the Scheduler's callback URL is never passed through `isSSRFSafeURL()`, which blocks requests to RFC-1918 private addresses, loopback, and cloud metadata endpoints. An admin can configure a scheduled task with an internal network `callbackURL` to perform SSRF against cloud infrastructure metadata services or internal APIs not otherwise reachable from the internet. Version 26.0 contains a patch for the issue.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

AVideo before 26.0 has a server-side request forgery issue in the Scheduler plugin. A user with admin privileges can configure a callback URL that makes the server contact internal systems or cloud metadata services. This mainly threatens sensitive internal data exposure, not broad unauthenticated compromise.

Executive priority

Treat as a timely maintenance and exposure-reduction item, especially for cloud-hosted AVideo. Prioritize upgrade if administrators are numerous, third-party managed, or if the server can reach sensitive internal APIs.

Technical view

The Scheduler plugin run() path in plugin/Scheduler/Scheduler.php passes admin-configurable callbackURL to url_get_contents() after only isValidURL() format validation. It does not apply isSSRFSafeURL(), which is intended to block private, loopback, and cloud metadata targets. Fixed in AVideo 26.0.

Likely exposure

Exposure is limited to WWBN AVideo installations below 26.0 using the Scheduler plugin. Exploitation requires administrator privileges in AVideo, but impact can extend to internal services reachable from the AVideo server.

Exploitation context

The source bundle does not indicate active exploitation, and CISA KEV status is false. The issue is lower likelihood because it requires admin access, but it can become significant in cloud or segmented environments where the AVideo server can reach sensitive internal endpoints.

Researcher notes

This is CWE-918 SSRF with high privileges required. The key code distinction is format validation through isValidURL() without SSRF safety validation via isSSRFSafeURL(). Sources name 26.0 as patched; no separate workaround is provided.

Mitigation direction

  • Upgrade WWBN AVideo to version 26.0 or later.
  • Review vendor advisory and commit for exact remediation details.
  • Audit Scheduler plugin tasks for unexpected or internal callback URLs.
  • Restrict AVideo server egress to only required destinations where feasible.
  • Limit and monitor AVideo administrator accounts.

Validation and detection

  • Inventory AVideo deployments and identify versions below 26.0.
  • Confirm whether the Scheduler plugin is enabled or used.
  • Review scheduled task callbackURL values for internal, loopback, or metadata destinations.
  • Verify the patched validation is present after upgrade.
  • Check logs for unusual Scheduler outbound requests.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-33237 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N1.24.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2026-33237Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WWBNAVideo< 26.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.