dbcve.org
AvideoApplication · Wwbn

CVE-2026-28501

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 24.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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 24.0, an unauthenticated SQL Injection vulnerability exists in AVideo within the objects/videos.json.php and objects/video.php components. The application fails to properly sanitize the catName parameter when it is supplied via a JSON-formatted POST request body. Because JSON input is parsed and merged into $_REQUEST after global security checks are executed, the payload bypasses the existing sanitization mechanisms. This issue has been patched in version 24.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

An unauthenticated SQL Injection vulnerability exists in AVideo versions prior to 24.0 within objects/videos.json.php and objects/video.php. The catName parameter in JSON-formatted POST requests is not properly sanitized, and because JSON input is parsed into $_REQUEST after global security checks execute, the payload bypasses existing sanitization mechanisms.

MitigationUpgrade to AVideo version 24.0 or later. As a critical SQL injection, immediate patching is recommended to prevent unauthenticated remote attackers from executing arbitrary SQL queries.

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:< 24.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. Confirm AVideo installation
    Identify if AVideo (also known as Wwbn AVideo) is present on the system by locating AVideo-specific files, directories, or web application signatures.
    Affected if AVideo is installed on the system
  2. Determine installed AVideo version
    Locate and inspect the version file or configuration that contains the AVideo version number. This is typically found in version-related files, release notes, or the software metadata within the AVideo installation directory.
    Affected if The installed version cannot be determined or is less than 24.0
  3. Verify vulnerable endpoints exist
    Check for the presence of the files objects/videos.json.php and objects/video.php in the webroot or AVideo installation directory.
    Affected if Both vulnerable PHP files exist in the expected locations
  4. Check JSON POST handling on vulnerable endpoints
    Inspect the source code of objects/videos.json.php and objects/video.php to confirm they accept JSON-formatted POST requests and process the catName parameter.
    Affected if The code shows these endpoints accept JSON input and process the catName parameter from the request body
  5. Confirm version is within affected range
    Compare your confirmed installed version against the affected range: versions prior to 24.0 (any version < 24.0).
    Affected if The installed AVideo version is 23.x or earlier

The environment is affected if AVideo is installed with a version less than 24.0 and the vulnerable endpoint files (objects/videos.json.php or objects/video.php) are present and accessible.

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 24.0 or later
Fixed in 24.0
Vendor patch github.com →
Interim mitigation

Upgrade to AVideo version 24.0 or later. As a critical SQL injection, immediate patching is recommended to prevent unauthenticated remote attackers from executing arbitrary SQL queries.

Recommended fix High confidence

AVideo version 24.0 or later

  1. 1. Back up the current AVideo installation and database before proceeding with any changes.
  2. 2. Download AVideo version 24.0 or later from the official repository (https://github.com/WWBN/AVideo).
  3. 3. Replace the existing AVideo files with the new version 24.0 files, preserving configuration and media files.
  4. 4. Run any database migration scripts included in the upgrade if applicable.
  5. 5. Verify the upgrade was successful by checking that the application functions normally.
  6. 6. Confirm the vulnerability is fixed by testing that the catName parameter in objects/videos.json.php and objects/video.php is properly sanitized.
Caveat Major version upgrade may introduce compatibility changes with existing plugins or custom configurations; test thoroughly in a staging environment before production deployment

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-28501 — 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-28501 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