In this page, we documents security fixes in sdoc-server.
Level of issues:
- Critical: Issues that allow an attacker to control the server, completely wipe its data, or easily access files through anonymous users who lack permission.
- High:
- There is a way for users to access API they donβt have permission to access, but they need to know the library ID or other information first.
- SQL injections
3.0
3.0.9 (2026-11-09)
High
- Fixed SQL injection risk: use parameter binding for operation log queries and switch to mysql2 prepared statements at database layer.
- Fixed API path tampering risk: validate and encode document, comment and reply IDs to prevent special characters from altering request paths.
Medium
- Fixed download link and redirect risk: only allow HTTP/HTTPS download links without embedded credentials; disable automatic redirect following for Seahub API and content downloads. This is request boundary hardening and does not fully block all SSRF vectors.
- Fixed missing rate limiting on HTTP endpoints: default to maximum 600 requests per IP per minute with 429 response on throttling, and support trusted proxy configuration.
2.0
2.0.14 (2026-11-20)
- Fixed the the scurity issue in sdoc-server authentication validation, socket handling.
2.0.13 (2026-11-12)
Refer to v3.0.9