dbcve.org
Avideo EncoderApplication · Wwbn

CVE-2026-29058

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 7.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
AVideo is a video-sharing Platform software. Prior to version 7.0, an unauthenticated attacker can execute arbitrary OS commands on the server by injecting shell command substitution into the base64Url GET parameter. This can lead to full server compromise, data exfiltration (e.g., configuration secrets, internal keys, credentials), and service disruption. This issue has been patched in version 7.0.

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 confidence

AVideo versions prior to 7.0 contain an unauthenticated OS command injection vulnerability. Attackers can inject shell command substitution into the base64Url GET parameter, allowing execution of arbitrary operating system commands on the server and leading to full server compromise.

MitigationUpgrade AVideo to version 7.0 or later to remediate this vulnerability. If immediate upgrade is not possible, consider restricting access to the affected endpoint at the network level.

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
Avideo EncoderApplication
Affected:< 7.0

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if AVideo Encoder is installed
    Locate the AVideo installation directory or check for web server content related to AVideo. Common indicators include directories named 'AVideo', 'encoder', or web server configs pointing to AVideo paths.
    Affected if The target is running any version of Wwbn Avideo Encoder
  2. Determine installed AVideo Encoder version
    Check the version information in the AVideo installation - typically found in a version file, about page, or admin panel. Compare your version number against the 7.0 threshold.
    Affected if Installed version is any version prior to 7.0 (e.g., 6.x, 5.x, etc.)
  3. Verify base64Url parameter endpoint is accessible
    Test for the presence of the vulnerable endpoint by making a request to the AVideo Encoder interface and checking if the base64Url GET parameter is accepted.
    Affected if The base64Url parameter endpoint is reachable without authentication and processes base64-encoded input
  4. Confirm no network-level restrictions exist
    Determine if the affected endpoint is exposed to unauthenticated network access. Check firewall rules, network ACLs, or web server authentication settings.
    Affected if The endpoint accepts unauthenticated requests from external or untrusted sources

A user is affected if they are running Wwbn Avideo Encoder version prior to 7.0 and the base64Url parameter endpoint is accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 7.0 or later
Fixed in 7.0
Interim mitigation

Upgrade AVideo to version 7.0 or later to remediate this vulnerability. If immediate upgrade is not possible, consider restricting access to the affected endpoint at the network level.

Recommended fix High confidence

7.0

  1. Backup the current AVideo Encoder installation and database before proceeding with any changes
  2. Download AVideo Encoder version 7.0 from the official GitHub repository (github.com)
  3. Replace all existing AVideo Encoder files with the files from version 7.0
  4. Verify file permissions are correctly set after the upgrade
  5. Restart any relevant services (web server, application services)
  6. Confirm the application is functioning correctly and accessible
  7. Test that the base64Url parameter is properly sanitized and no longer accepts command injection payloads

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Avideo Encoder Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29058 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29058 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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