dbcve.org
AvideoApplication · Wwbn

CVE-2022-34652

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 description 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

SQL injection vulnerability in WWBN AVideo's Live Schedules plugin where the description parameter is not properly sanitized, allowing attackers to inject malicious SQL queries through HTTP requests to the ObjectYPT functionality.

MitigationImplement parameterized queries (prepared statements) and proper input validation for the description parameter in the Live Schedules plugin to prevent SQL injection.

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 AVideo installation directory and check the version file or metadata (commonly found in version.php, about.php, or the admin dashboard).
    Affected if The installed version is 11.6 or falls within the affected range.
  2. Confirm Live Schedules plugin is present
    Check the plugins directory for the 'LiveSchedules' or 'Live Schedules' plugin folder, or list enabled plugins in the AVideo admin panel.
    Affected if The Live Schedules plugin is installed and enabled.
  3. Verify ObjectYPT functionality is accessible
    Check if the ObjectYPT endpoint is accessible by reviewing the plugin's PHP files for the ObjectYPT class/function and confirming the route is registered.
    Affected if The ObjectYPT functionality is present and exposed via HTTP.
  4. Inspect description parameter handling
    Examine the Live Schedules plugin code (likely in a file like LiveSchedules.php or liveSchedule.php) for how the 'description' parameter is processed in database queries.
    Affected if The code directly uses the description parameter in SQL queries without visible sanitization or prepared statements.

You are affected if you are running AVideo version 11.6, have the Live Schedules plugin enabled, and the description parameter in ObjectYPT is handled without parameterized 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (prepared statements) and proper input validation for the description parameter in the Live Schedules plugin to prevent SQL injection.

Recommended fix Moderate confidence

AVideo 12.0 or latest stable release

  1. 1. Identify the current AVideo installation version by checking the admin dashboard or version file
  2. 2. Navigate to the official AVideo GitHub repository or download page
  3. 3. Download the latest stable release (version 12.0 or later)
  4. 4. Back up the entire AVideo installation directory and database before upgrading
  5. 5. Replace the existing files with the new version files
  6. 6. Run any database migration scripts if included in the upgrade
  7. 7. Verify the Live Schedules plugin is updated to the latest compatible version
  8. 8. Test the application functionality, particularly the Live Schedules feature
Caveat Review release notes for potential breaking changes between 11.6 and the target version, particularly regarding plugin compatibility

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

Fix this in Avideo Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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