Lees weergave
BookStack v25.12.5
This release specifically addresses folder permission issues (often showing as an error when attempting to access content) which could occur from changes introduced in v25.12.4.
Links
Full List of Changes
This release contains the following fixes and changes:
- Updated filter caching folder handling to avoid server filesystem permission issues. (#6023)
v11.15.4
β¨ New Features & Improvements
- @directus/app
- Added collaboration state (is viewing, is editing) and minor design updates (#26574 by @alvarosabu)
π Bug Fixes & Optimizations
- @directus/app
- Fixed translation interface being disabled when delete permission not allowed (#26669 by @AlexGaillard)
- Fixed item comparison failing when special characters are present in manual primary keys (#26668 by @AlexGaillard)
- Fixed non-editable state for relational fields with custom permissions (#26676 by @HZooly)
- Added restriction of allowed MIME types to the system file upload interface (#26646 by @AlexGaillard)
- @directus/api
- Added restriction of allowed MIME types to the system file upload interface (#26646 by @AlexGaillard)
π¦ Published Versions
@directus/app@15.4.0@directus/api@33.3.1
BookStack v25.12.4
Security Release
BookStack v25.12.4 has been released.
This is a security release to address a vulnerability where style code in page content could be used to manipulate the page beyond the expected content area, opening up risk of potential phishing and/or tracking by bad page editors.
We advise that you update your instance if you allow untrusted users to create or edit pages.
Thanks to SeongYun Moon (@Moonster8282 on GitHub) for their responsible discovery and reporting of this issue.
Additional Update Notices
- Page Content - As of this release, extra layers of filtering have been applied to page content. While we have tried to ensure this has minimal impact on content, it's possible this will lead to extra elements being filtered.
- Option Change - The
ALLOW_CONTENT_SCRIPTSenv option is now considered deprecated. It's advised to use theAPP_CONTENT_FILTERINGoption, as documented here, instead if needed.
If you experience issues with your page content being over-filtered feel free to raise an issue on GitHub where we can check if the behaviour is intentional or something which needs to be patched.
You can use the new page content filtering option, with a value of jhf which should match the prior version filtering, but this will remove a layer of content filtering security so is not recommend.
Full List of Changes
- Added new option for more granular page filter control.
- Updated page content filtering to detect extra cases, and to apply a more aggressive allow-list style filter.
- Updated application PHP dependencies.