CVE-2026-39368
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWWBN AVideo is an open source video platform. In versions 26.0 and prior, the Live restream log callback flow accepted an attacker-controlled restreamerURL and later fetched that stored URL server-side, enabling stored SSRF for authenticated streamers. The vulnerable flow allowed a low-privilege user with streaming permission to store an arbitrary callback URL and trigger server-side requests to loopback or internal HTTP services through the restream log feature.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceWWBN AVideo versions 26.0 and prior contain a stored Server-Side Request Forgery (SSRF) vulnerability in the Live restream log callback flow. Authenticated streamers with low-privilege streaming permissions can store an attacker-controlled restreamerURL in the callback configuration, which the server later fetches server-side, allowing requests to internal services such as loopback addresses or internal HTTP endpoints.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 26.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify AVideo installation and versionLocate the AVideo installation directory and check the version.php or version file, or look at the dashboard About page to confirm the exact version number installedAffected if The installed version is 26.0 or lower
-
Verify Live streaming module is enabledCheck if the Live streaming functionality is active in the AVideo control panel under Plugins or Live sectionAffected if Live streaming is enabled and accessible to users
-
Check user permission configurationExamine user roles and permissions in the AVideo admin panel to determine if low-privilege users (non-admin streamers) have access to Live restream settingsAffected if Users with streaming-only permissions can access or modify restream configuration
-
Inspect restream callback URL configurationLook in the Live plugin settings or database for the restreamerURL parameter in the restream callback flow; check tables like plugins, live_transmition, or related configuration tablesAffected if A restreamerURL is configured or can be set by low-privilege users
-
Check for existing internal network callbacksReview current restream callback URLs in the system configuration or database to see if any point to 127.0.0.1, localhost, or private IP ranges (10.x.x.x, 172.16-31.x.x, 192.168.x.x)Affected if The restream callback URL is set to an internal or loopback address
You are affected if running AVideo version 26.0 or lower with Live streaming enabled and low-privilege users can configure restream callback URLs that could target internal network addresses.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict allowlist validation on the restreamerURL parameter to only permit trusted external endpoints, disable server-side fetching of user-supplied URLs in the callback feature, or add network segmentation controls to prevent the application server from reaching internal services.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39368 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39368 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data