dbcve.org
AvideoApplication · Wwbn

CVE-2022-33148

HIGH · 8.8 CVSS v3.1 Published 2022-08-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A sql injection vulnerability exists in the ObjectYPT functionality of WWBN AVideo 11.6 and dev master commit 3f7c0364. A specially-crafted HTTP request can lead to a SQL injection. An attacker can send an HTTP request to trigger this vulnerability.This vulnerability exists in the Live Schedules plugin, allowing an attacker to inject SQL by manipulating the title parameter.

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

A SQL injection vulnerability exists in the Live Schedules plugin of WWBN AVideo versions 11.6 and dev master (commit 3f7c0364). Attackers can inject malicious SQL commands through the title parameter in ObjectYPT functionality via specially-crafted HTTP requests. This high-severity (CVSS 8.8) flaw allows attackers to potentially access, modify, or delete database contents.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in the Live Schedules plugin, specifically validating and sanitizing the title parameter input. Apply the latest security patch from the vendor.

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:= 11.6

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

CVSS:3.1/AV:N/AC:L/PR:L/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 version
    Locate the version file or header in your AVideo installation (typically in version.php, index.php, or admin panel about page) and compare the version number to 11.6
    Affected if The installed version is 11.6 or the dev master branch around commit 3f7c0364
  2. Locate the Live Schedules plugin
    Check the plugin directory for the Live Schedules plugin (commonly in plugin/LiveSchedule or similar path) and verify it exists in your installation
    Affected if The Live Schedules plugin is present in the plugins directory
  3. Verify ObjectYPT functionality is enabled
    Check the AVideo admin panel for the ObjectYPT feature or examine the plugin configuration file to determine if this functionality is active
    Affected if ObjectYPT functionality is enabled in the plugin or system configuration
  4. Inspect the title parameter handling code
    Examine the Live Schedules plugin code that handles the title parameter (look for SQL query construction involving the title field in ObjectYPT-related files)
    Affected if The code directly uses the title parameter in dynamic SQL queries without parameterization or input sanitization
  5. Check HTTP request handling for the vulnerable endpoint
    Review the HTTP request handler for the ObjectYPT endpoint in the Live Schedules plugin and verify how the title parameter is processed
    Affected if The title parameter from HTTP requests is passed directly into SQL statements without prepared statements or escaping

Your environment is affected if you are running AVideo version 11.6 or dev master with the Live Schedules plugin and ObjectYPT functionality enabled, where the title parameter is processed in dynamic SQL queries.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements in the Live Schedules plugin, specifically validating and sanitizing the title parameter input. Apply the latest security patch from the vendor.

Fix this in Avideo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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