<?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>Sat, 17 Oct 2026 19:07:10 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-162946</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-162946</link>
      <description>EUVD-2026-162946</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-162946</guid>
    </item>
    <item>
      <title>fkie_cve-2023-46725</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-46725</link>
      <description>&lt;p&gt;FoodCoopShop is open source software for food coops and local shops. Versions starting with 3.2.0 prior to 3.6.1 are vulnerable to server-side request forgery. In the Network module, a manufacturer account can use the `/api/updateProducts.json` endpoint to make the server send a request to an arbitrary host. This means that the server can be used as a proxy into the internal network where the server is. Furthermore, the checks on a valid image are not adequate, leading to a time of check time of use issue. For example, by using a custom server that returns 200 on HEAD requests, then return a valid image on first GET request and then a 302 redirect to final target on second GET request, the server will copy whatever file is at the redirect destination, making this a full SSRF. Version 3.6.1 fixes this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;FoodCoopShop is open source software for food coops and local shops. Versions starting with 3.2.0 prior to 3.6.1 are vulnerable to server-side request forgery. In the Network module, a manufacturer account can use the `/api/updateProducts.json` endpoint to make the server send a request to an arbitrary host. This means that the server can be used as a proxy into the internal network where the server is. Furthermore, the checks on a valid image are not adequate, leading to a time of check time of use issue. For example, by using a custom server that returns 200 on HEAD requests, then return a valid image on first GET request and then a 302 redirect to final target on second GET request, the server will copy whatever file is at the redirect destination, making this a full SSRF. Version 3.6.1 fixes this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-46725</guid>
    </item>
    <item>
      <title>GHSA-jhww-fx2j-3rf7 — FoodCoopShop Server-Side Request Forgery vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jhww-fx2j-3rf7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: foodcoopshop/foodcoopshop&lt;/p&gt;
&lt;p&gt;There is a potential SSRF vulnerability in foodcoopshop. Since there is no security policy on your Github, I tried to use the emails to contact you.&lt;/p&gt;
&lt;p&gt;The potential issue is in the Network module, where a manufacturer account can use the /api/updateProducts.json endpoint to make the server send a request to arbitrary host.
For example, use
```
data[data][0][remoteProductId]=352&amp;amp;data[data][0][image]=http://localhost:8888/
```
will make the server send a request to localhost:8888. This means that it can be used as a proxy into the internal network where the server is.&lt;/p&gt;
&lt;p&gt;To make matters worse, the checks on valid image is not enough. There is time of check time of use issue there.
For example, by using a custom server that returns 200 on HEAD requests, then return a valid image on first GET request and then a 302 redirect to final target on second GET request, the server will copy whatever file
at the redirect destination, making this a full SSRF.
(An example python server that can do this is at https://pastebin.com/8K5Brwbq This will make the server download whatever at the redirect target)&lt;/p&gt;
&lt;p&gt;You can check https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html for more information on SSRF, their impact and how to properly fix it.&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: foodcoopshop/foodcoopshop&lt;/p&gt;
&lt;p&gt;There is a potential SSRF vulnerability in foodcoopshop. Since there is no security policy on your Github, I tried to use the emails to contact you.&lt;/p&gt;
&lt;p&gt;The potential issue is in the Network module, where a manufacturer account can use the /api/updateProducts.json endpoint to make the server send a request to arbitrary host.
For example, use
```
data[data][0][remoteProductId]=352&amp;amp;data[data][0][image]=http://localhost:8888/
```
will make the server send a request to localhost:8888. This means that it can be used as a proxy into the internal network where the server is.&lt;/p&gt;
&lt;p&gt;To make matters worse, the checks on valid image is not enough. There is time of check time of use issue there.
For example, by using a custom server that returns 200 on HEAD requests, then return a valid image on first GET request and then a 302 redirect to final target on second GET request, the server will copy whatever file
at the redirect destination, making this a full SSRF.
(An example python server that can do this is at https://pastebin.com/8K5Brwbq This will make the server download whatever at the redirect target)&lt;/p&gt;
&lt;p&gt;You can check https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html for more information on SSRF, their impact and how to properly fix it.&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jhww-fx2j-3rf7</guid>
    </item>
    <item>
      <title>gsd-2023-46725</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-46725</link>
      <description>gsd-2023-46725</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-46725</guid>
    </item>
  </channel>
</rss>
