CVE-2026-45274
MediumCVSS 6.9Summary
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.
Risk Assessment
Bypassing the registration policy may allow unauthorized individuals to create accounts and gain access to user-level features, potentially serving as a stepping stone for further attacks.
Recommendation
Update MyBooks to version 3.42.0 or later to remediate this vulnerability.
Original NVD description (English source)
MyBooks is anebook management web server also known as Talebook. In 3.41.2 and earlier, the SignUp.post handler for POST /api/user/sign_up in webserver/handlers/user.py does not enforce the ALLOW_REGISTER configuration flag, even though the frontend hides registration controls when the flag is false. An unauthenticated remote attacker can call the endpoint directly and create a valid account on an instance whose administrator disabled public registration. The process_auth_header function in webserver/handlers/base.py also does not verify the account's active flag, so the newly created and unactivated account can authenticate immediately and access user-level API functionality. The bypass defeats the intended account-creation policy and can supply the low-privilege account required by related authorization vulnerabilities. This issue is fixed in version 3.42.0.