What is the CVSS score of CVE-2026-35181?

CVE-2026-35181 has a CVSS 3.1 base score of 4.3 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N. EPSS exploitation probability: 0.0%.

PHP CVE-2026-35181

MEDIUM

Cross-Site Request Forgery (CSRF) (CWE-352)

2026-04-03 https://github.com/WWBN/AVideo

GHSA-4q27-4rrq-fx95

CSRF PHP

4.3

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

4.3 MEDIUM

AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Apr 04, 2026 - 00:30 vuln.today

CVE Published

Apr 03, 2026 - 23:43 nvd

MEDIUM 4.3

DescriptionGitHub Advisory

Severity: Medium CWE: CWE-352 (Cross-Site Request Forgery)

Summary

The player skin configuration endpoint at admin/playerUpdate.json.php does not validate CSRF tokens. The plugins table is explicitly excluded from the ORM's domain-based security check via ignoreTableSecurityCheck(), removing the only other layer of defense. Combined with SameSite=None cookies, a cross-origin POST can modify the video player appearance on the entire platform.

Details

In admin/playerUpdate.json.php at line 17, the player skin is set directly from POST data:

php

$pluginDO->skin = $_POST['skin'];

No CSRF token is validated anywhere in the endpoint. Normally, the ORM layer performs a Referer/Origin domain check as a secondary defense against cross-origin writes. However, the plugins table is registered in ignoreTableSecurityCheck(), which explicitly bypasses this ORM-level protection for plugin configuration.

AVideo's session cookies are configured with SameSite=None, meaning the admin's authenticated session cookie is automatically included in cross-origin POST requests from any website.

An attacker can craft a page that, when visited by an authenticated admin, silently changes the player skin to any value, including potentially invalid or disruptive configurations.

Proof of Concept

Host the following HTML on an attacker-controlled domain:

html

<!DOCTYPE html>
<html>
<head><title>CSRF Player Skin</title></head>
<body>
<h1>Loading video...</h1>
<form id="csrf" method="POST"
      action="https://your-avideo-instance.com/admin/playerUpdate.json.php">
  <input type="hidden" name="skin" value="minimalist" />
</form>
<script>
  document.getElementById("csrf").submit();
</script>
</body>
</html>

When an authenticated admin visits this page, the platform's player skin is changed without their knowledge.

Impact

Platform-wide player appearance modification without admin consent
Potential disruption of video playback if an invalid skin value is set
The ORM security bypass via ignoreTableSecurityCheck() means there is no fallback protection
Can be used as part of a broader defacement or social engineering attack

Recommended Fix

Add CSRF token validation at admin/playerUpdate.json.php, before processing POST data:

php

// admin/playerUpdate.json.php (before line 17)
if (!isGlobalTokenValid()) {
    die('{"error":"Invalid CSRF token"}');
}

--- *Found by aisafe.io*

AnalysisAI

Cross-site request forgery (CSRF) in AVideo's player skin configuration endpoint allows unauthenticated remote attackers to modify the video player appearance platform-wide when an authenticated administrator visits a malicious webpage. The vulnerability stems from missing CSRF token validation combined with disabled ORM-level domain security checks and SameSite=None cookie configuration; a proof-of-concept demonstrates silent modification of player skin settings without admin consent.

Technical ContextAI

AVideo is a PHP-based video platform that uses an ORM layer for database operations. The vulnerable endpoint at admin/playerUpdate.json.php processes POST requests to update player skin configuration in the plugins table. Normally, the ORM implements a secondary Referer/Origin domain-based security check to prevent cross-origin writes. However, the plugins table is explicitly registered in the ignoreTableSecurityCheck() method, which bypasses this defense. Additionally, session cookies are configured with SameSite=None, allowing the authenticated administrator's session cookie to be automatically included in cross-origin POST requests. The root cause is CWE-352: the application performs a sensitive state-changing operation (POST to playerUpdate.json.php line 17: $pluginDO->skin = $_POST['skin']) without validating a CSRF token or maintaining the only remaining security layer (ORM domain check). The affected product is WWBN/AVideo (CPE: pkg:composer/wwbn_avideo), a Composer-based PHP package.

RemediationAI

Add CSRF token validation to the admin/playerUpdate.json.php endpoint before line 17 (before the player skin is set from POST data). The recommended fix is to call isGlobalTokenValid() and terminate with an error response if validation fails: insert if (!isGlobalTokenValid()) { die('{"error":"Invalid CSRF token"}'); } at the beginning of POST processing. Additionally, review and re-enable the ORM-level domain security check for the plugins table by removing it from ignoreTableSecurityCheck(), and consider updating cookie configuration to use SameSite=Strict or SameSite=Lax instead of SameSite=None to restore cookie isolation for cross-origin requests. Consult the GitHub Security Advisory at https://github.com/WWBN/AVideo/security/advisories/GHSA-4q27-4rrq-fx95 for the recommended patched version and deployment instructions.