Understand vulnerabilities. Protect your applications.
Discover which vulnerabilities affect your technologies and how to fix them. Explore clear explanations, affected versions and practical recommendations - from CMS platforms and plugins to application libraries.
Vulnerability archive 51
Reset filtersKirby: System path exposure from error messages in the REST API
Kirby: File upload permissions are not checked during processing of chunk data
Kirby: Access to image files and limited access to JSON files outside of the site root via path traversal in the media handling
Kirby: `pages.access` permission is not checked in the `site/find` REST API route
Kirby: Access to files of top-level drafts is not protected by permissions
Kirby: External Initialization of the Panel on reverse proxy setups with the `Forwarded` header
Kirby: Cross-site scripting (XSS) from incomplete HTML/XML sanitization in `Dom::sanitize()`
Kirby: Request header injection in `Http\Remote`
Kirby: Self cross-site scripting (self-XSS) in the writer field
Kirby: `pages.access` permission is not checked in the pages picker for parent pages
Kirby CMS vulnerable to cross-site scripting (XSS) from links in KirbyTags and image blocks in the site frontend
Kirby CMS's content locks disclose IDs and emails of inaccessible users from `users.access/list` permissions
Kirby CMS has pre-authentication path traversal and PHP file inclusion during user lookup
Kirby CMS's `pages.access` permission is not checked during rendering of page drafts
Kirby CMS vulnerable to cross-site scripting (XSS) from list field content in the site frontend
Kirby CMS has an Arbitrary Method Call via REST API Search and Collection Query Endpoints
Kirby CMS's system API endpoint leaks installed version and license data to authenticated users
Kirby CMS doesn't gate user avatar creation, replacement and deletion with user update permissions
Kirby CMS's read access to site, user and role information is not gated by permissions
Kirby CMS's `pages.access/list` and `files.access/list` permissions are not consistently checked in the Panel and REST API
Kirby is vulnerable to authorization bypass during page, file and user creation via blueprint injection
Kirby's page creation API bypasses the changeStatus permission check via unfiltered isDraft parameter
Kirby has Server-Side Template Injection (SSTI) via double template resolution in option rendering
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.