Releases2
Frequency3 years 7 months
Last Release
A Python wrapper for BookStack's API

CVE History

CVEAffectedPublishedCVSS v3CVSS v2
= 23.10.26.5 MEDIUM

Book Stack version 23.10.2 allows filtering local files on the server. This is possible because the application is vulnerable to SSRF.

< 23.082.4 LOW

Server-Side Request Forgery (SSRF) in GitHub repository bookstackapp/bookstack prior to v23.08.

< 22.095.4 MEDIUM

Cross-site scripting vulnerability in BookStack versions prior to v22.09 allows a remote authenticated attacker to inject an arbitrary script.

< 22.02.35.4 MEDIUM3.5 LOW

Cross-site Scripting (XSS) - Stored in GitHub repository bookstackapp/bookstack prior to v22.02.3.

< 21.12.16.5 MEDIUM4 MEDIUM

bookstack is vulnerable to Improper Access Control

<= 21.11.29.8 CRITICAL7.5 HIGH

bookstack is vulnerable to Improper Access Control

< 21.116.8 MEDIUM4 MEDIUM

bookstack is vulnerable to Cross-Site Request Forgery (CSRF)

< 21.11.24.3 MEDIUM4 MEDIUM

bookstack is vulnerable to Improper Access Control

< 21.10.35.7 MEDIUM3.5 LOW

bookstack is vulnerable to Unrestricted Upload of File with Dangerous Type

< 21.10.36.5 MEDIUM4 MEDIUM

bookstack is vulnerable to Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

< 21.10.16.5 MEDIUM4 MEDIUM

bookstack is vulnerable to Unrestricted Upload of File with Dangerous Type

< 21.08.56.5 MEDIUM4 MEDIUM

bookstack is vulnerable to Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

< 21.08.25.4 MEDIUM3.5 LOW

bookstack is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

< 21.08.25.4 MEDIUM3.5 LOW

bookstack is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

< 21.086.5 MEDIUM4 MEDIUM

bookstack is vulnerable to Server-Side Request Forgery (SSRF)

< 0.30.56.4 MEDIUM5.5 MEDIUM

BookStack is a platform for storing and organising information and documentation. In BookStack before version 0.30.5, a user with permissions to edit a page could set certain image URL's to manipulate functionality in the exporting system, which would allow them to make server side requests and/or have access to a wider scope of files within the BookStack file storage locations. The issue was addressed in BookStack v0.30.5. As a workaround, page edit permissions could be limited to only those that are trusted until you can upgrade.

< 0.30.47.7 HIGH3.5 LOW

In BookStack before version 0.30.4, a user with permissions to edit a page could insert JavaScript code through the use of `javascript:` URIs within a link or form which would run, within the context of the current page, when clicked or submitted. Additionally, a user with permissions to edit a page could insert a particular meta tag which could be used to silently redirect users to a alternative location upon visit of a page. Dangerous content may remain in the database but will be removed before being displayed on a page. If you think this could have been exploited the linked advisory provides a SQL query to test. As a workaround without upgrading, page edit permissions could be limited to only those that are trusted until you can upgrade although this will not address existing exploitation of this vulnerability. The issue is fixed in BookStack version 0.30.4.

< 0.30.47.7 HIGH3.5 LOW

In BookStack before version 0.30.4, a user with permissions to edit a page could add an attached link which would execute untrusted JavaScript code when clicked by a viewer of the page. Dangerous content may remain in the database after this update. If you think this could have been exploited the linked advisory provides a SQL query to test. As a workaround, page edit permissions could be limited to only those that are trusted until you can upgrade although this will not address existing exploitation of this vulnerability. The issue is fixed in version 0.30.4.

>= 0.18.0, < 0.29.26.3 MEDIUM3.5 LOW

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.