Talebook CVE-2026-45272

Requires an authenticated administrator account (PR:H) able to reach the AdminSettings.post handler in webserver/handlers/admin.py, and the ability to submit a SOCIAL_AUTH setting key containing quote/newline characters that break out of the generated dictionary in auto.py. Reliable code execution additionally depends on the settings file being re-imported: the described path sets autoreload to true so restart_async triggers a process-supervisor restart and re-import of auto.py - without a restart/reload the injected module is not executed. Exploitation is limited to versions 3.41.2 and earlier; standalone use is gated by admin privilege, though vendor-noted authorization and registration flaws may lower that barrier in a chained attack.

This is a genuine high-priority issue for anyone running Talebook, but its real-world blast radius is bounded by the PR:H requirement in the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:N) - exploitation as a standalone bug needs administrator access, which is why it is a privileged-RCE rather than an internet-spray worm. The vendor explicitly notes related authorization and registration weaknesses (reflected in the commit's active-user check in base.py and the ALLOW_REGISTER gate in user.py) that could chain to reduce the required privilege, which materially raises concern. No EPSS score, no KEV listing, and no POC were provided, so the numeric high score (9.4) is driven by impact (VC/VI/VA:H and scope change) rather than by demonstrated ease of exploitation; treat the 9.4 as an impact-weighted ceiling, not evidence of imminent mass exploitation. Given that the fix is public and the code diff plainly reveals the injection point, any operator - even a mid-sized municipal library IT team in inowroclaw - should treat patching as urgent because the vulnerable pattern is easy to reverse-engineer from the commit. Bottom line: real priority to patch, but not an unauthenticated remote catastrophe absent the chained pre-conditions.

An attacker who has (or obtains via a chained registration/authorization weakness) an administrator session submits a settings update whose SOCIAL_AUTH key name contains a quote and newline that closes the settings dictionary and appends attacker-chosen Python statements. They also enable autoreload, prompting the process supervisor to restart the service, which imports the poisoned auto.py and executes the payload as the service account. No public POC is identified at time of analysis, but the fixing commit makes the injection mechanics straightforward to reconstruct.