<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-15T22:07:52.093515+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-49279</id>
    <title>fkie_cve-2026-49279</title>
    <updated>2026-10-15T22:07:52.108047+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>WWBN AVideo is an open source video platform. Versions 29.0 and below contain a Stored XSS vulnerability through the autoEvalCodeOnHTML parameter in the MessageSQLite WebSocket Handler. The MessageSQLite.php handler only strips autoEvalCodeOnHTML from $json['msg'], but msgToResourceId() reads from $msg['json'] with higher priority. An attacker can place the XSS payload in the json key instead of msg, bypassing the sanitization entirely. An authenticated attacker can execute arbitrary JavaScript in any connected user's browser session via the WebSocket messaging system, stealing session cookies and authentication tokens, taking over accounts through session hijacking, and chaining with CSRF to perform admin actions on the victim's behalf, in the default SQLite WebSocket backend configuration. This issue has a patch that has yet to be officially released, see https://github.com/WWBN/AVideo/commit/3e0b3ce2bfa766183ff0ae227439394db57b1a23.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-49279"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-2fhx-q92v-5fhv</id>
    <title>GHSA-2fhx-q92v-5fhv — WWBN AVideo: Stored XSS via autoEvalCodeOnHTML Bypass in MessageSQLite WebSocket Handler (CVE-2026-43874 Bypass)</title>
    <updated>2026-10-15T22:07:52.108133+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: wwbn/avideo</p>
<p># AVideo: Stored XSS via `autoEvalCodeOnHTML` in MessageSQLite WebSocket Handler</p>
<p>## Summary</p>
<p>AVideo has a stored XSS vulnerability in the WebSocket messaging system. The `MessageSQLite.php` handler only strips `autoEvalCodeOnHTML` from `$json['msg']`, but `msgToResourceId()` reads from `$msg['json']` with higher priority. An attacker can place the XSS payload in the `json` key instead of `msg`, bypassing the sanitization entirely.</p>
<p>## Affected Versions</p>
<p>AVideo &lt;= latest</p>
<p>## Vulnerability Details</p>
<p>### Root Cause: Shallow sanitization only covers `$json['msg']`</p>
<p>`plugin/YPTSocket/MessageSQLite.php` lines 268-271 — the incomplete fix:</p>
<p>```php
if (empty($msgObj-&gt;isCommandLineInterface) &amp;&amp; ($msgObj-&gt;sentFrom ?? '') !== 'php') {
    if (is_array($json['msg'] ?? null)) {
        unset($json['msg']['autoEvalCodeOnHTML']);  // Only strips from $json['msg']
    }
}
```</p>
<p>`plugin/YPTSocket/MessageSQLite.php` lines 361-367 — the bypass via `msgToResourceId()`:</p>
<p>```php
if (!empty($msg['json'])) {
    $obj['msg'] = $msg['json'];       // $msg['json']['autoEvalCodeOnHTML'] is NEVER stripped
} else if (!empty($msg['msg'])) {
    $obj['msg'] = $msg['msg'];        // Only this path was sanitized
} else {
    $obj['msg'] = $msg;
}
```</p>
<p>Compare with the correctly patched `Message.php` (lines 254-256):</p>
<p>```php
$json = removeAutoEvalCodeOnHTMLRecursive($json);  // Strips from ALL nested paths
```</p>
<p>And `MessageSQLiteV2.php` (lines 302-303):</p>
<p>```php
$json = removeAutoEvalCodeOnHTMLRecursive($json)…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-2fhx-q92v-5fhv"/>
  </entry>
</feed>
