MyBooks vulnerabilities

MyBooks (Talebook) version 3.41.2 and earlier does not enforce the ALLOW_REGISTER configuration flag in the SignUp.post handler, allowing an unauthenticated attacker to create an account even when the administrator disabled public registration. Additionally, the process_auth_header function does not verify the account's active flag, so a newly created unactivated account can authenticate immediately and access user-level API functionality. This issue is fixed in version 3.42.0.

MyBooks (Talebook) in version 3.41.2 and earlier contains a vulnerability in the handling of SOCIAL_AUTH key names in the AdminSettings.post handler. These names are concatenated without proper escaping into the auto.py file, allowing an administrator to inject arbitrary Python code. The code is executed during module import, enabling command execution with service privileges.

MyBooks (Talebook) in version 3.41.2 and earlier has a vulnerability in the AdminSettings.post handler for POST /api/admin/settings, which does not check the self.admin_user property despite having the auth decorator. Any authenticated regular user can overwrite server configuration values including SMTP credentials, OAuth client secrets, storage paths, and security feature flags. Additionally, the process_auth_header function fails to verify the account's active flag, allowing unactivated accounts to authenticate. This issue is fixed in version 3.42.0.