<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 22 Oct 2026 07:44:57 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-278243</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-278243</link>
      <description>EUVD-2026-278243</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-278243</guid>
    </item>
    <item>
      <title>fkie_cve-2026-34375</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-34375</link>
      <description>&lt;p&gt;WWBN AVideo is an open source video platform. In versions up to and including 26.0, the YPTWallet Stripe payment confirmation page directly echoes the `$_REQUEST[&amp;#39;plugin&amp;#39;]` parameter into a JavaScript block without any encoding or sanitization. The `plugin` parameter is not included in any of the framework&amp;#39;s input filter lists defined in `security.php`, so it passes through completely raw. An attacker can inject arbitrary JavaScript by crafting a malicious URL and sending it to a victim user. The same script block also outputs the current user&amp;#39;s username and password hash via `User::getUserName()` and `User::getUserPass()`, meaning a successful XSS exploitation can immediately exfiltrate these credentials. Commit fa0bc102493a15d79fe03f86c07ab7ca1b5b63e2 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;WWBN AVideo is an open source video platform. In versions up to and including 26.0, the YPTWallet Stripe payment confirmation page directly echoes the `$_REQUEST[&amp;#39;plugin&amp;#39;]` parameter into a JavaScript block without any encoding or sanitization. The `plugin` parameter is not included in any of the framework&amp;#39;s input filter lists defined in `security.php`, so it passes through completely raw. An attacker can inject arbitrary JavaScript by crafting a malicious URL and sending it to a victim user. The same script block also outputs the current user&amp;#39;s username and password hash via `User::getUserName()` and `User::getUserPass()`, meaning a successful XSS exploitation can immediately exfiltrate these credentials. Commit fa0bc102493a15d79fe03f86c07ab7ca1b5b63e2 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-34375</guid>
    </item>
    <item>
      <title>GHSA-pm37-62g7-p768 — AVideo Vulnerable to Reflected XSS via Unsanitized plugin Parameter in YPTWallet Stripe Payment Page</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pm37-62g7-p768</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: wwbn/avideo&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The YPTWallet Stripe payment confirmation page directly echoes the `$_REQUEST[&amp;#39;plugin&amp;#39;]` parameter into a JavaScript block without any encoding or sanitization. The `plugin` parameter is not included in any of the framework&amp;#39;s input filter lists defined in `security.php`, so it passes through completely raw. An attacker can inject arbitrary JavaScript by crafting a malicious URL and sending it to a victim user.&lt;/p&gt;
&lt;p&gt;The same script block also outputs the current user&amp;#39;s username and password hash via `User::getUserName()` and `User::getUserPass()`, meaning a successful XSS exploitation can immediately exfiltrate these credentials.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The Stripe confirmation page renders the `plugin` parameter directly into a `&amp;lt;script&amp;gt;` block:&lt;/p&gt;
&lt;p&gt;```php
// plugin/YPTWallet/plugins/YPTWalletStripe/confirmButton.php:116
&amp;#34;plugin&amp;#34;: &amp;#34;&amp;lt;?php echo @$_REQUEST[&amp;#39;plugin&amp;#39;]; ?&amp;gt;&amp;#34;,
```&lt;/p&gt;
&lt;p&gt;This appears inside a `$.ajax()` data object within a `&amp;lt;script&amp;gt;` tag. Because the value is injected into a JavaScript string context (not HTML), standard HTML entity encoding would not be sufficient even if it were applied. However, no encoding of any kind is performed.&lt;/p&gt;
&lt;p&gt;The `plugin` parameter is not present in any of the sanitization or filtering arrays in `security.php`, so it arrives completely unmodified.&lt;/p&gt;
&lt;p&gt;Immediately adjacent to the injection point, the script also exposes user credentials:&lt;/p&gt;
&lt;p&gt;```php
// plugin/YPTWallet/plugins/YPTWalletStripe/confirmButton.php:117-118
&amp;#34;user&amp;#34;: &amp;#34;&amp;lt;?php echo User::getUserName()…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: wwbn/avideo&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The YPTWallet Stripe payment confirmation page directly echoes the `$_REQUEST[&amp;#39;plugin&amp;#39;]` parameter into a JavaScript block without any encoding or sanitization. The `plugin` parameter is not included in any of the framework&amp;#39;s input filter lists defined in `security.php`, so it passes through completely raw. An attacker can inject arbitrary JavaScript by crafting a malicious URL and sending it to a victim user.&lt;/p&gt;
&lt;p&gt;The same script block also outputs the current user&amp;#39;s username and password hash via `User::getUserName()` and `User::getUserPass()`, meaning a successful XSS exploitation can immediately exfiltrate these credentials.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The Stripe confirmation page renders the `plugin` parameter directly into a `&amp;lt;script&amp;gt;` block:&lt;/p&gt;
&lt;p&gt;```php
// plugin/YPTWallet/plugins/YPTWalletStripe/confirmButton.php:116
&amp;#34;plugin&amp;#34;: &amp;#34;&amp;lt;?php echo @$_REQUEST[&amp;#39;plugin&amp;#39;]; ?&amp;gt;&amp;#34;,
```&lt;/p&gt;
&lt;p&gt;This appears inside a `$.ajax()` data object within a `&amp;lt;script&amp;gt;` tag. Because the value is injected into a JavaScript string context (not HTML), standard HTML entity encoding would not be sufficient even if it were applied. However, no encoding of any kind is performed.&lt;/p&gt;
&lt;p&gt;The `plugin` parameter is not present in any of the sanitization or filtering arrays in `security.php`, so it arrives completely unmodified.&lt;/p&gt;
&lt;p&gt;Immediately adjacent to the injection point, the script also exposes user credentials:&lt;/p&gt;
&lt;p&gt;```php
// plugin/YPTWallet/plugins/YPTWalletStripe/confirmButton.php:117-118
&amp;#34;user&amp;#34;: &amp;#34;&amp;lt;?php echo User::getUserName()…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pm37-62g7-p768</guid>
    </item>
  </channel>
</rss>
