<?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-19T10:54:41.180302+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-281099</id>
    <title>EUVD-2026-281099</title>
    <updated>2026-10-19T10:54:41.183491+00:00</updated>
    <content>EUVD-2026-281099</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-281099"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-35179</id>
    <title>fkie_cve-2026-35179</title>
    <updated>2026-10-19T10:54:41.183539+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 26.0 and prior, the SocialMediaPublisher plugin exposes a publishInstagram.json.php endpoint that acts as an unauthenticated proxy to the Facebook/Instagram Graph API. The endpoint accepts user-controlled parameters including an access token, container ID, and Instagram account ID, and passes them directly to the Graph API via InstagramUploader::publishMediaIfIsReady(). This allows any unauthenticated user to make arbitrary Graph API calls through the server, potentially using stolen tokens or abusing the platform's own credentials.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-35179"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-x9w5-xccw-5h9w</id>
    <title>GHSA-x9w5-xccw-5h9w — AVideo: Unauthenticated Instagram Graph API Proxy via publishInstagram.json.php</title>
    <updated>2026-10-19T10:54:41.183591+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>The SocialMediaPublisher plugin exposes a `publishInstagram.json.php` endpoint that acts as an unauthenticated proxy to the Facebook/Instagram Graph API. The endpoint accepts user-controlled parameters including an access token, container ID, and Instagram account ID, and passes them directly to the Graph API via `InstagramUploader::publishMediaIfIsReady()`. This allows any unauthenticated user to make arbitrary Graph API calls through the server, potentially using stolen tokens or abusing the platform's own credentials.</p>
<p>## Details</p>
<p>At `plugin/SocialMediaPublisher/publishInstagram.json.php:14`, the endpoint passes request parameters directly to the Instagram Graph API without any authentication check:</p>
<p>```php
InstagramUploader::publishMediaIfIsReady(
    $_REQUEST['accessToken'],
    $_REQUEST['containerId'],
    $_REQUEST['instagramAccountId']
);
```</p>
<p>There is no call to `User::isLogged()`, `User::isAdmin()`, or any other authorization check before processing the request.</p>
<p>In contrast, sibling endpoints in the same plugin enforce proper authorization:
- `uploadVideo.json.php` requires `User::isLogged()`
- `refresh.json.php` requires `User::isAdmin()`</p>
<p>The endpoint was confirmed accessible on a live instance: it returns a Graph API error response, demonstrating that it processes the request and forwards it to Facebook's servers.</p>
<p>## Proof of Concept</p>
<p>1. Send a request to the endpoint without any authentication:</p>
<p>```bash
curl -s "https://your-avideo-instance.com/…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-x9w5-xccw-5h9w"/>
  </entry>
</feed>
