<?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>Thu, 08 Oct 2026 15:48:21 +0000</lastBuildDate>
    <item>
      <title>cnvd-2020-35507</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2020-35507</link>
      <description>cnvd-2020-35507</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2020-35507</guid>
    </item>
    <item>
      <title>EUVD-2026-40362</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-40362</link>
      <description>EUVD-2026-40362</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-40362</guid>
    </item>
    <item>
      <title>fkie_cve-2020-11055</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-11055</link>
      <description>&lt;p&gt;In BookStack greater than or equal to 0.18.0 and less than 0.29.2, there is an XSS vulnerability in comment creation. A user with permission to create comments could POST HTML directly to the system to be saved in a comment, which would then be executed/displayed to others users viewing the comment. Through this vulnerability custom JavaScript code could be injected and therefore ran on other user machines. This most impacts scenarios where not-trusted users are given permission to create comments. This has been fixed in 0.29.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In BookStack greater than or equal to 0.18.0 and less than 0.29.2, there is an XSS vulnerability in comment creation. A user with permission to create comments could POST HTML directly to the system to be saved in a comment, which would then be executed/displayed to others users viewing the comment. Through this vulnerability custom JavaScript code could be injected and therefore ran on other user machines. This most impacts scenarios where not-trusted users are given permission to create comments. This has been fixed in 0.29.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-11055</guid>
    </item>
    <item>
      <title>GHSA-5vf7-q87h-pg6w — Cross-Site Scripting in BookStack</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5vf7-q87h-pg6w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: ssddanbrown/bookstack&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A user with permission to create comments could POST HTML directly to the system to be saved in a comment, which would then be executed/displayed to others users viewing the comment. Through this vulnerability custom JavaScript code could be injected and therefore ran on other user machines.&lt;/p&gt;
&lt;p&gt;This most impacts scenarios where not-trusted users are given permission to create comments.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue was addressed in BookStack v0.29.2.&lt;/p&gt;
&lt;p&gt;After upgrading, The command `php artisan bookstack:regenerate-comment-content` should be ran to remove any pre-existing dangerous content.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Comments can be disabled in the system settings to prevent them being shown to users. Alternatively, comment creation permissions can be altered as required to only those who are trusted but this will not address existing exploitation of this vulnerability.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;* [BookStack Beta v0.29.2](https://github.com/BookStackApp/BookStack/releases/tag/v0.29.2)
* JVN#41035278
* [BookStack Blog Post](https://bookstackapp.com/blog/beta-release-v0-29-2/)&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory:
* Open an issue in [the BookStack GitHub repository](BookStackApp/BookStack/issues).
* Ask on the [BookStack Discord chat](https://discord.gg/ztkBqR2).
* Follow the [BookStack Security Advice](https://github.com/BookStackApp/BookStack#-security) to contact someone privately.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: ssddanbrown/bookstack&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A user with permission to create comments could POST HTML directly to the system to be saved in a comment, which would then be executed/displayed to others users viewing the comment. Through this vulnerability custom JavaScript code could be injected and therefore ran on other user machines.&lt;/p&gt;
&lt;p&gt;This most impacts scenarios where not-trusted users are given permission to create comments.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue was addressed in BookStack v0.29.2.&lt;/p&gt;
&lt;p&gt;After upgrading, The command `php artisan bookstack:regenerate-comment-content` should be ran to remove any pre-existing dangerous content.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Comments can be disabled in the system settings to prevent them being shown to users. Alternatively, comment creation permissions can be altered as required to only those who are trusted but this will not address existing exploitation of this vulnerability.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;* [BookStack Beta v0.29.2](https://github.com/BookStackApp/BookStack/releases/tag/v0.29.2)
* JVN#41035278
* [BookStack Blog Post](https://bookstackapp.com/blog/beta-release-v0-29-2/)&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory:
* Open an issue in [the BookStack GitHub repository](BookStackApp/BookStack/issues).
* Ask on the [BookStack Discord chat](https://discord.gg/ztkBqR2).
* Follow the [BookStack Security Advice](https://github.com/BookStackApp/BookStack#-security) to contact someone privately.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5vf7-q87h-pg6w</guid>
    </item>
    <item>
      <title>gsd-2020-11055</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-11055</link>
      <description>gsd-2020-11055</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-11055</guid>
    </item>
    <item>
      <title>jvndb-2020-000031</title>
      <link>https://cve.radiocsirt.org/vuln/jvndb-2020-000031</link>
      <description>&lt;p&gt;BookStack contains a cross-site scripting vulnerability (CWE-79).&#13;
&#13;
Kenichi Okuno of Mitsui Bussan Secure Directions, Inc reported this vulnerability to IPA.&#13;
JPCERT/CC coordinated with the developer under Information Security Early Warning Partnership.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;BookStack contains a cross-site scripting vulnerability (CWE-79).&#13;
&#13;
Kenichi Okuno of Mitsui Bussan Secure Directions, Inc reported this vulnerability to IPA.&#13;
JPCERT/CC coordinated with the developer under Information Security Early Warning Partnership.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/jvndb-2020-000031</guid>
    </item>
  </channel>
</rss>
