<?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 16:52:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-31114 — backpack/crud Vulnerable to Cross-site Scripting</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-31114</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Laravel-Backpack CRUD&lt;/p&gt;
&lt;p&gt;backpack/crud provides Create, Read, Update &amp;amp; Delete (CRUD) functions for Backpack, a collection of Laravel packages that help users build custom administration panels. Versions prior to 5.0.13, 4.1.69, and 4.0.63 are vulnerable to cross-site scripting. An attacker could conduct a targeted phishing campaign, in order to trick users or admins into clicking a malicious link, which under very specific circumstances could give them information or possibly admin access. Versions 5.0.13, 4.1.69, and 4.0.63 patch the issue. As a workaround, manually look inside error views in `resources/views/errors` and output `e($exception-&amp;gt;getMessage())` instead of `$exception-&amp;gt;getMessage()`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Laravel-Backpack CRUD&lt;/p&gt;
&lt;p&gt;backpack/crud provides Create, Read, Update &amp;amp; Delete (CRUD) functions for Backpack, a collection of Laravel packages that help users build custom administration panels. Versions prior to 5.0.13, 4.1.69, and 4.0.63 are vulnerable to cross-site scripting. An attacker could conduct a targeted phishing campaign, in order to trick users or admins into clicking a malicious link, which under very specific circumstances could give them information or possibly admin access. Versions 5.0.13, 4.1.69, and 4.0.63 patch the issue. As a workaround, manually look inside error views in `resources/views/errors` and output `e($exception-&amp;gt;getMessage())` instead of `$exception-&amp;gt;getMessage()`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-31114</guid>
    </item>
  </channel>
</rss>
