dbcve.org
AvideoApplication · Wwbn

CVE-2026-33352

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

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
WWBN AVideo is an open source video platform. Prior to version 26.0, an unauthenticated SQL injection vulnerability exists in `objects/category.php` in the `getAllCategories()` method. The `doNotShowCats` request parameter is sanitized only by stripping single-quote characters (`str_replace("'", '', ...)`), but this is trivially bypassed using a backslash escape technique to shift SQL string boundaries. The parameter is not covered by any of the application's global input filters in `objects/security.php`. Version 26.0 contains a patch for the issue.

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

Unauthenticated SQL injection in WWBN AVideo prior to v26.0 within objects/category.php's getAllCategories() method. The doNotShowCats parameter is inadequately sanitized using only str_replace to remove single quotes, which can be bypassed via backslash escape to shift SQL string boundaries and inject arbitrary SQL commands.

MitigationUpgrade to version 26.0 or later which contains the patch. Until patched, consider deploying a WAF rule to block SQL injection patterns in the doNotShowCats parameter.

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
AvideoApplication
Affected:< 26.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 AVideo installation and version
    Locate the AVideo installation directory and check the version file (typically in version.txt or within the main index.php)
    Affected if The installed version is below 26.0 (e.g., 25.x, 24.x, etc.)
  2. Verify vulnerable file exists
    Confirm objects/category.php exists in the web root
    Affected if The file exists and the server is running a version below 26.0
  3. Inspect the getAllCategories method
    Open objects/category.php and locate the getAllCategories() function to observe how the doNotShowCats parameter is handled
    Affected if The method uses only str_replace to sanitize doNotShowCats without parameterized queries or proper escaping
  4. Confirm unauthenticated access path
    Test accessing the category endpoint without any authentication credentials (e.g., via curl or browser to objects/category.php?doNotShowCats=test)
    Affected if The endpoint responds without requiring authentication and accepts the doNotShowCats parameter

The environment is affected if AVideo version is below 26.0 and the objects/category.php file handles doNotShowCats with only basic str_replace sanitization 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 26.0 or later
Fixed in 26.0
Vendor patch github.com →
Interim mitigation

Upgrade to version 26.0 or later which contains the patch. Until patched, consider deploying a WAF rule to block SQL injection patterns in the doNotShowCats parameter.

Recommended fix High confidence

Version 26.0

  1. Upgrade AVideo to version 26.0 or later to resolve the SQL injection vulnerability
  2. Alternatively, if immediate upgrade is not feasible, apply the patch from commit 206d38e97b8c854771bb2907b13f9f36e8bcf874 to objects/category.php
  3. After applying the fix, verify the getAllCategories() function no longer accepts unsanitized input via the doNotShowCats parameter

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

Fix this in Avideo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33352 — 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-33352 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