<?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>Wed, 28 Oct 2026 16:18:46 +0000</lastBuildDate>
    <item>
      <title>cnvd-2017-32552</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2017-32552</link>
      <description>cnvd-2017-32552</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2017-32552</guid>
    </item>
    <item>
      <title>EUVD-2026-80768</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-80768</link>
      <description>EUVD-2026-80768</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-80768</guid>
    </item>
    <item>
      <title>fkie_cve-2017-1000093</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2017-1000093</link>
      <description>&lt;p&gt;Poll SCM Plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request Forgery attacks. This allowed attackers to initiate polling of projects with a known name. While Jenkins in general does not consider polling to be a protection-worthy action as it&amp;#39;s similar to cache invalidation, the plugin specifically adds a permission to be able to use this functionality, and this issue undermines that permission.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Poll SCM Plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request Forgery attacks. This allowed attackers to initiate polling of projects with a known name. While Jenkins in general does not consider polling to be a protection-worthy action as it&amp;#39;s similar to cache invalidation, the plugin specifically adds a permission to be able to use this functionality, and this issue undermines that permission.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2017-1000093</guid>
    </item>
    <item>
      <title>GHSA-fv3c-6cw7-2qcq — Jenkins Poll SCM Plugin vulnerable to Cross-Site Request Forgery</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fv3c-6cw7-2qcq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.jenkins-ci.plugins:pollscm&lt;/p&gt;
&lt;p&gt;Jenkins Poll SCM Plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request Forgery attacks. This allowed attackers to initiate polling of projects with a known name. While Jenkins in general does not consider polling to be a protection-worthy action as it&amp;#39;s similar to cache invalidation, the plugin specifically adds a permission to be able to use this functionality, and this issue undermines that permission. This functionality now is only available via POST.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.jenkins-ci.plugins:pollscm&lt;/p&gt;
&lt;p&gt;Jenkins Poll SCM Plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request Forgery attacks. This allowed attackers to initiate polling of projects with a known name. While Jenkins in general does not consider polling to be a protection-worthy action as it&amp;#39;s similar to cache invalidation, the plugin specifically adds a permission to be able to use this functionality, and this issue undermines that permission. This functionality now is only available via POST.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fv3c-6cw7-2qcq</guid>
    </item>
    <item>
      <title>gsd-2017-1000093</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2017-1000093</link>
      <description>gsd-2017-1000093</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2017-1000093</guid>
    </item>
  </channel>
</rss>
