dbcve.org
AvideoApplication · Wwbn

CVE-2026-33770

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-27
Fix available
A fix is available. Upgrade to after 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. In versions up to and including 26.0, the `fixCleanTitle()` static method in `objects/category.php` constructs a SQL SELECT query by directly interpolating both `$clean_title` and `$id` into the query string without using prepared statements or parameterized queries. An attacker who can trigger category creation or renaming with a crafted title value can inject arbitrary SQL. Commit 994cc2b3d802b819e07e6088338e8bf4e484aae4 contains a patch.

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

SQL injection vulnerability in WWBN AVideo (versions up to 26.0) where the `fixCleanTitle()` method in `objects/category.php` directly interpolates user-controlled `$clean_title` and `$id` parameters into SQL queries without parameterized queries. Attackers with ability to create or rename categories can inject arbitrary SQL commands.

MitigationApply the patch in commit 994cc2b3d802b819e07e6088338e8bf4e484aae4 to replace direct string interpolation with prepared statements, or upgrade to a patched version.

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 installed AVideo version
    Locate the version file or admin panel to determine the running version of Wwbn AVideo. Common locations include a version.php file or the dashboard.
    Affected if The installed version is 26.0 or lower.
  2. Verify category.php exists
    Check for the presence of the file objects/category.php in the web root or application directory.
    Affected if The file objects/category.php exists on the system.
  3. Locate the vulnerable fixCleanTitle method
    Open objects/category.php and search for the function definition 'function fixCleanTitle'.
    Affected if The fixCleanTitle method is present in the file.
  4. Inspect SQL query construction in fixCleanTitle
    Within the fixCleanTitle function, examine how the $clean_title and $id parameters are used in SQL queries. Look for direct string concatenation or interpolation (e.g., $db->query("SELECT ... WHERE clean_title = '$clean_title'").
    Affected if The code uses direct string interpolation of $clean_title or $id into SQL queries without using prepared statements or parameter binding.
  5. Assess category management access
    Determine if the category creation or renaming functionality is accessible to users. Check user roles and permissions related to category management in the admin panel or database.
    Affected if Users have the ability to create new categories or rename existing ones.

If the system runs AVideo version 26.0 or lower, contains the vulnerable fixCleanTitle method in objects/category.php with direct SQL interpolation, and allows users to create or rename categories, the environment is affected by this SQL injection vulnerability.

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 a release after 26.0
Vendor patch github.com →
Interim mitigation

Apply the patch in commit 994cc2b3d802b819e07e6088338e8bf4e484aae4 to replace direct string interpolation with prepared statements, or upgrade to a patched version.

Recommended fix High confidence
  1. Review the vendor patch at commit 994cc2b3d802b819e07e6088338e8bf4e484aae4 to understand the code changes
  2. Apply the patch to objects/category.php in your AVideo installation
  3. The fix replaces direct SQL string interpolation with prepared statements/parameterized queries for the $clean_title and $id variables in the fixCleanTitle() method
  4. Verify the fix was applied correctly by examining the updated code
  5. Test category creation/renaming functionality to ensure the patch does not break legitimate operations

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

Fix this in Avideo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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