Only the most current stable version receives patches for security vulnerabilities.
supported_version: 5.1.0
Report suspected security vulnerabilities to librebooking@outlook.com.
LibreBooking is maintained by a small volunteer team. Please allow 2-5 days for an initial response. If the issue is confirmed, a patch will be released as soon as practical depending on severity, complexity, and maintainer availability.
Reports should include:
- Affected LibreBooking version or commit
- Attacker role and prerequisites
- Clear reproduction steps
- Request/response examples or screenshots, where applicable
- Expected behavior and actual behavior
- Security impact
- Whether the issue has been publicly disclosed
Reports that only include scanner output, code-search results, AI-generated summaries, or references to historical CVEs without a working reproduction against a supported LibreBooking version may be closed without investigation.
Reports about the following issues may be handled as hardening requests or non-security bugs rather than security vulnerabilities unless accompanied by a clear exploit path and security impact:
- Missing security headers
- Version disclosure
- Self-XSS
- Logout CSRF
- Issues that require administrator privileges, or administrator-authored content, without crossing a lower-privilege security boundary (see Trusted Content)
- Dependency CVEs without evidence that vulnerable code is reachable in LibreBooking
- Theoretical issues without reproduction steps
- Social engineering or physical attacks
- Denial-of-service reports based only on excessive traffic volume
LibreBooking does not request, assign, or coordinate CVE IDs.
Security issues may be fixed in public commits, release notes, or GitHub advisories at the maintainers' discretion. Reporters who want a CVE must coordinate it independently and should not expect maintainer participation.
Reports submitted primarily to obtain CVE assignment will be closed. Do not submit reports solely to request CVE assignment. We do not provide CVE sponsorship, CVE write-ups, embargo coordination for CVE publication, or repeated status updates for CVE records.
Grant application, group, resource, and schedule administrator permissions only to trusted users. Administrators can change configuration, users, groups, resources, schedules, announcements, reservations, templates, and other content that may be displayed to other users or sent by email.
LibreBooking treats administrator accounts as privileged operators, not as untrusted users. A malicious or compromised administrator account can affect the confidentiality, integrity, and availability of a LibreBooking installation. Use strong passwords, revoke unused administrator access, and assign the smallest administrator role needed for the user's responsibilities.
LibreBooking treats content authored by trusted administrators within their granted permissions as trusted for security triage purposes. Some administrative fields intentionally allow rich text, email or notification template markup, or custom HTML/CSS, and that content may be displayed to other users or unauthenticated visitors.
Reports about HTML or script injection through administrator-authored content are welcome, but the project may handle them as defense-in-depth hardening or ordinary bugs rather than security vulnerabilities when exploitation requires administrator permissions. An administrator who can author this content is already a privileged operator (see Administrator Trust Model).
LibreBooking may add or improve HTML sanitization for administrator-authored content, but the absence of sanitization on content that requires administrator permissions to create is not, by itself, treated as a security boundary.
In contrast, injection issues remain security issues where the content's author has lower privilege than the viewer, for example content authored by an unauthenticated or ordinary user that executes in another user's or an administrator's session. This includes user-submitted custom attribute values or other non-administrator-authored content.