<?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://vulnerability.circl.lu</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, 29 Sep 2026 18:55:38 +0000</lastBuildDate>
    <item>
      <title>cnvd-2022-55728</title>
      <link>https://vulnerability.circl.lu/vuln/cnvd-2022-55728</link>
      <description>cnvd-2022-55728</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cnvd-2022-55728</guid>
    </item>
    <item>
      <title>fkie_cve-2021-25116</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2021-25116</link>
      <description>&lt;p&gt;The Enqueue Anything WordPress plugin through 1.0.1 does not have authorisation and CSRF checks in the remove_asset AJAX action, and does not ensure that the item to be deleted is actually an asset. As a result, low privilege users such as subscriber could delete arbitrary assets, as well as put arbitrary posts in the trash.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Enqueue Anything WordPress plugin through 1.0.1 does not have authorisation and CSRF checks in the remove_asset AJAX action, and does not ensure that the item to be deleted is actually an asset. As a result, low privilege users such as subscriber could delete arbitrary assets, as well as put arbitrary posts in the trash.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2021-25116</guid>
    </item>
    <item>
      <title>GHSA-qj28-v8qh-ccqw</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-qj28-v8qh-ccqw</link>
      <description>&lt;p&gt;The Enqueue Anything WordPress plugin through 1.0.1 does not have authorisation and CSRF checks in the remove_asset AJAX action, and does not ensure that the item to be deleted is actually an asset. As a result, low privilege users such as subscriber could delete arbitrary assets, as well as put arbitrary posts in the trash.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Enqueue Anything WordPress plugin through 1.0.1 does not have authorisation and CSRF checks in the remove_asset AJAX action, and does not ensure that the item to be deleted is actually an asset. As a result, low privilege users such as subscriber could delete arbitrary assets, as well as put arbitrary posts in the trash.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-qj28-v8qh-ccqw</guid>
    </item>
    <item>
      <title>gsd-2021-25116</title>
      <link>https://vulnerability.circl.lu/vuln/gsd-2021-25116</link>
      <description>gsd-2021-25116</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/gsd-2021-25116</guid>
    </item>
  </channel>
</rss>
