<?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, 07 Oct 2026 23:45:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-7051 — Blog2Social: Social Media Auto Post &amp; Scheduler &lt;= 8.9.0 - Missing Authorization to Authenticated (Subscriber+) Delete…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-7051</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pr-gateway Blog2Social: Social Media Auto Post &amp;amp; Scheduler&lt;/p&gt;
&lt;p&gt;The Blog2Social: Social Media Auto Post &amp;amp; Scheduler plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 8.9.0. This is due to a missing ownership verification in the B2S_Post_Tools::deleteUserPublishPost() and B2S_Post_Tools::deleteUserSchedPost() functions, neither function includes a blog_user_id constraint in its database query, allowing authenticated attackers to soft-delete any user&amp;#39;s B2S post records by supplying arbitrary sequential wp_b2s_posts.id values via the &amp;#39;postId&amp;#39; parameter. This makes it possible for authenticated attackers to delete other users&amp;#39; published and scheduled social media post records, disrupting content publishing workflows.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pr-gateway Blog2Social: Social Media Auto Post &amp;amp; Scheduler&lt;/p&gt;
&lt;p&gt;The Blog2Social: Social Media Auto Post &amp;amp; Scheduler plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 8.9.0. This is due to a missing ownership verification in the B2S_Post_Tools::deleteUserPublishPost() and B2S_Post_Tools::deleteUserSchedPost() functions, neither function includes a blog_user_id constraint in its database query, allowing authenticated attackers to soft-delete any user&amp;#39;s B2S post records by supplying arbitrary sequential wp_b2s_posts.id values via the &amp;#39;postId&amp;#39; parameter. This makes it possible for authenticated attackers to delete other users&amp;#39; published and scheduled social media post records, disrupting content publishing workflows.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-7051</guid>
    </item>
  </channel>
</rss>
