<?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>Tue, 06 Oct 2026 19:44:35 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-325775</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-325775</link>
      <description>EUVD-2026-325775</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-325775</guid>
    </item>
    <item>
      <title>fkie_cve-2026-8365</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-8365</link>
      <description>&lt;p&gt;The Blocksy theme for WordPress is vulnerable to PHP Object Injection leading to Remote Code Execution via the &amp;#39;blocksy_meta&amp;#39; REST API field and the V200 database migration in versions up to and including 2.1.35. This is due to insufficient input sanitization in the blocksy_sanitize_post_meta_options() function, which only blocks values containing &amp;#39;&amp;lt;&amp;#39; or &amp;#39;&amp;gt;&amp;#39; and does not prevent serialized PHP object strings from being stored in post meta, combined with the SearchReplacer::run_recursively() function unconditionally deserializing all string values via @unserialize() during migration without restricting allowed classes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject a serialized Blocksy\RaiiPattern object into post meta that, when the V200 migration runs on an upgraded site, is deserialized and triggers RaiiPattern::__destruct(), which executes arbitrary PHP callables via call_user_func().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Blocksy theme for WordPress is vulnerable to PHP Object Injection leading to Remote Code Execution via the &amp;#39;blocksy_meta&amp;#39; REST API field and the V200 database migration in versions up to and including 2.1.35. This is due to insufficient input sanitization in the blocksy_sanitize_post_meta_options() function, which only blocks values containing &amp;#39;&amp;lt;&amp;#39; or &amp;#39;&amp;gt;&amp;#39; and does not prevent serialized PHP object strings from being stored in post meta, combined with the SearchReplacer::run_recursively() function unconditionally deserializing all string values via @unserialize() during migration without restricting allowed classes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject a serialized Blocksy\RaiiPattern object into post meta that, when the V200 migration runs on an upgraded site, is deserialized and triggers RaiiPattern::__destruct(), which executes arbitrary PHP callables via call_user_func().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-8365</guid>
    </item>
    <item>
      <title>GHSA-r622-c48h-h6qq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r622-c48h-h6qq</link>
      <description>&lt;p&gt;The Blocksy theme for WordPress is vulnerable to PHP Object Injection leading to Remote Code Execution via the &amp;#39;blocksy_meta&amp;#39; REST API field and the V200 database migration in versions up to and including 2.1.35. This is due to insufficient input sanitization in the blocksy_sanitize_post_meta_options() function, which only blocks values containing &amp;#39;&amp;lt;&amp;#39; or &amp;#39;&amp;gt;&amp;#39; and does not prevent serialized PHP object strings from being stored in post meta, combined with the SearchReplacer::run_recursively() function unconditionally deserializing all string values via @unserialize() during migration without restricting allowed classes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject a serialized Blocksy\RaiiPattern object into post meta that, when the V200 migration runs on an upgraded site, is deserialized and triggers RaiiPattern::__destruct(), which executes arbitrary PHP callables via call_user_func().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Blocksy theme for WordPress is vulnerable to PHP Object Injection leading to Remote Code Execution via the &amp;#39;blocksy_meta&amp;#39; REST API field and the V200 database migration in versions up to and including 2.1.35. This is due to insufficient input sanitization in the blocksy_sanitize_post_meta_options() function, which only blocks values containing &amp;#39;&amp;lt;&amp;#39; or &amp;#39;&amp;gt;&amp;#39; and does not prevent serialized PHP object strings from being stored in post meta, combined with the SearchReplacer::run_recursively() function unconditionally deserializing all string values via @unserialize() during migration without restricting allowed classes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject a serialized Blocksy\RaiiPattern object into post meta that, when the V200 migration runs on an upgraded site, is deserialized and triggers RaiiPattern::__destruct(), which executes arbitrary PHP callables via call_user_func().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r622-c48h-h6qq</guid>
    </item>
  </channel>
</rss>
