AVideo has SQL Injection via Partial Prepared Statement — videos_id Concatenated Directly into Query

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-33767: 0.52% estimated exploitation activity in the next 30 days; percentile 44.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary In objects/like.php, the getLike() method constructs a SQL query using a prepared statement placeholder (?) for usersid but directly concatenates $this-videosid into the query string without parameterization. An attacker who can control the videosid value (via a crafted request) can inject arbitrary SQL, bypassing the partial prepared-statement protection. Details File: objects/like.php Vulnerable code: The query mixes a parameterized placeholder for usersid with raw string concatenation for videosid. The $this-videosid value originates from user-supplied request input (typically a POST/GET parameter identifying the video being liked/disliked) and is not cast to integer or validated before being embedded in the SQL string. All other queries in the same file correctly use ? placeholders for both columns: The inconsistency means any attacker who can submit a like/dislike action with a crafted videosid can inject SQL. Since like/dislike actions are typically available to any…

Published by the source

26 Mar 2026, 18:12 UTC

Last modified by the source

27 Mar 2026, 21:40 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fj74-qxj7-r3vc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33767

Advisory: AVideo has SQL Injection via Partial Prepared Statement — videos_id Concatenated Directly into Query
IDs: CVE-2026-33767, GHSA-fj74-qxj7-r3vc
Record: https://patchnext.com/advisories/cve-2026-33767 (revision 1, source checked 26 Oct 2026, 14:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: wwbn/avideo 26.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist wwbn/avideo: affected < 26.0; fixed in 26.0

## Suggested inspection (read-only)
- Packagist wwbn/avideo: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wwbn/avideo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fj74-qxj7-r3vc (GitHub-reviewed advisory GHSA-fj74-qxj7-r3vc lists affected ranges: Packagist wwbn/avideo >=0 <26.0)

Commands are suggestions: review each one before running it.