<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-17T18:12:33.391378+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/euvd-2026-277830</id>
    <title>EUVD-2026-277830</title>
    <updated>2026-10-17T18:12:33.393601+00:00</updated>
    <content>EUVD-2026-277830</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-277830"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33767</id>
    <title>fkie_cve-2026-33767</title>
    <updated>2026-10-17T18:12:33.393630+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>WWBN AVideo is an open source video platform. In versions up to and including 26.0, in `objects/like.php`, the `getLike()` method constructs a SQL query using a prepared statement placeholder (`?`) for `users_id` but directly concatenates `$this-&gt;videos_id` into the query string without parameterization. An attacker who can control the `videos_id` value (via a crafted request) can inject arbitrary SQL, bypassing the partial prepared-statement protection. Commit 0215d3c4f1ee748b8880254967b51784b8ac4080 contains a patch.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-33767"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-fj74-qxj7-r3vc</id>
    <title>GHSA-fj74-qxj7-r3vc — AVideo has SQL Injection via Partial Prepared Statement — videos_id Concatenated Directly into Query</title>
    <updated>2026-10-17T18:12:33.393662+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: wwbn/avideo</p>
<p>### Summary</p>
<p>In `objects/like.php`, the `getLike()` method constructs a SQL query using a prepared statement placeholder (`?`) for `users_id` but directly concatenates `$this-&gt;videos_id` into the query string without parameterization. An attacker who can control the `videos_id` value (via a crafted request) can inject arbitrary SQL, bypassing the partial prepared-statement protection.</p>
<p>### Details</p>
<p>**File:** `objects/like.php`</p>
<p>**Vulnerable code:**
```php
$sql = "SELECT * FROM likes WHERE users_id = ? AND videos_id = ".$this-&gt;videos_id." LIMIT 1;";
$res = sqlDAL::readSql($sql, "i", [$this-&gt;users_id]);
```</p>
<p>The query mixes a parameterized placeholder for `users_id` with raw string concatenation for `videos_id`. The `$this-&gt;videos_id` value originates from user-supplied request input (typically a POST/GET parameter identifying the video being liked/disliked) and is not cast to integer or validated before being embedded in the SQL string.</p>
<p>All other queries in the same file correctly use `?` placeholders for both columns:
```php
// Correct pattern used elsewhere:
$sql = "SELECT count(*) as total FROM likes WHERE videos_id = ? AND like = 1";
```</p>
<p>The inconsistency means any attacker who can submit a like/dislike action with a crafted `videos_id` can inject SQL. Since like/dislike actions are typically available to any authenticated user, the attack surface is broad.</p>
<p>### PoC</p>
<p>An attacker sends a like request with an injected `videos_id`:
```
POST /objects/likeAjax.json.php
video…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-fj74-qxj7-r3vc"/>
  </entry>
</feed>
