Security readout for executives and security teams
Plain-English summary
MyBooks, also known as Talebook, can let an administrator turn a settings change into code execution on the server. A successful attack could expose ebook data, alter files, establish persistence, or interrupt service. Systems before version 3.42.0 are affected.
Executive priority
Treat affected deployments as an urgent remediation item, especially where administration is externally reachable or account controls are weak. Prioritize upgrading to 3.42.0, restricting access during remediation, and investigating suspicious settings changes or restarts. The impact is critical, although confirmed exploitation is not established by the supplied evidence.
Technical view
The administrative settings handler accepts unsafe SOCIAL_AUTH key names. When settings are written, unescaped quotes or newlines can alter the generated auto.py Python source. MyBooks later imports that file, executing injected statements as the application service account. Enabling autoreload can trigger a supervised restart and subsequent import.
Likely exposure
Exposure is limited to PoxenStudio MyBooks/Talebook versions earlier than 3.42.0. Standalone exploitation requires administrator access, but related authorization or registration weaknesses may reduce that barrier when chained. Internet-accessible administration interfaces and weakly protected administrator accounts increase practical risk.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not identified as being in KEV. Exploitation is remotely reachable with low complexity after obtaining administrator privileges and requires no user interaction. Reported consequences affect confidentiality, integrity, and availability across the application and potentially connected resources.
Researcher notes
The weakness combines insufficient input validation with unsafe source generation and later module import. The documented trigger involves autoreload and process supervision. Authorization and registration issues are mentioned as possible chain components, but their exact versions and mechanics are not established here. Avoid assuming unauthenticated exploitation without separate evidence.
Mitigation direction
- Upgrade MyBooks/Talebook to version 3.42.0 or later.
- Restrict administrative access until the upgrade is complete.
- Review administrator accounts and revoke unexpected or unnecessary access.
- Rotate credentials and secrets if compromise indicators are found.
Validation and detection
- Identify every MyBooks/Talebook deployment and record its installed version.
- Confirm production instances run version 3.42.0 or later.
- Inspect auto.py for unexpected Python statements or malformed SOCIAL_AUTH entries.
- Review administrator activity, authentication events, service restarts, and file changes for anomalies.
- Verify administrative settings remain restricted to authorized accounts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-829: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-45272 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.4 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9.4CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/PoxenStudio/mybooks/security/advisories/GHSA-4wfr-9gcv-j638CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/PoxenStudio/mybooks/commit/a1780c98b00566af7da2fc099fe38500efc02e92CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/PoxenStudio/mybooks/releases/tag/3.42.0CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code
Improper Control of Generation of Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.