CVE-2026-107592 in Book Manager Plugin
Summary
by MITRE • 11/22/2026
The Mooberry Book Manager WordPress plugin through 4.16.2 does not perform any capability or nonce check in one of its AJAX actions, allowing any authenticated user with a minimal role such as Subscriber to change the publisher assigned to any book, including books created by other users, and to create new book records. The missing nonce check also makes the action exploitable via CSRF against any logged-in user.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/22/2026
The vulnerability identified in Mooberry Book Manager WordPress plugin versions through 4.16.2 represents a critical failure in access control mechanisms within an AJAX endpoint, specifically classified under CWE-352 as Cross-Site Request Forgery and CWE-862 as Missing Authorization Check. This flaw stems from the absence of both capability verification and nonce validation during the execution of specific administrative actions exposed via AJAX requests. In standard WordPress development practices, any action that modifies data or performs state-changing operations must verify that the requesting user possesses the necessary permissions for that specific task and include a unique cryptographic token to prevent unauthorized request submission. The plugin fails to implement these essential security controls, leaving the functionality wide open to exploitation by authenticated users with minimal privileges.
The operational impact of this vulnerability is significant due to the low barrier to entry required for exploitation. Any user account on the WordPress site that holds at least the Subscriber role can exploit this flaw without needing elevated administrative rights. This allows attackers who have compromised or created a basic subscriber-level account to manipulate core data within the application. Specifically, an attacker can alter the publisher information associated with any book record in the database, regardless of whether those books were originally created by other users or administrators. Furthermore, the lack of authorization checks permits the creation of new, unauthorized book records. This capability undermines the integrity and reliability of the book management system, potentially leading to data corruption, misleading metadata, or the injection of malicious content under false authorship or publisher attribution.
Beyond direct manipulation of existing records, the missing nonce check introduces a severe Cross-Site Request Forgery risk against any logged-in user on the site. An attacker can craft a malicious webpage containing hidden forms or JavaScript that automatically submits requests to the vulnerable AJAX endpoint when visited by an authenticated victim. Since WordPress sessions are typically maintained via cookies and do not require explicit re-authentication for subsequent requests within the same session, the server will process these forged requests as legitimate actions performed by the victim user. This mechanism allows attackers to force state changes without the knowledge or consent of the targeted individual, effectively bypassing standard security boundaries that rely on identity verification rather than intent validation.
To mitigate this vulnerability, immediate updates to version 4.16.3 or later are strongly recommended, as these versions include patches for the missing authorization and CSRF protections. For sites unable to update immediately due to compatibility constraints, temporary mitigations should focus on restricting access to the affected AJAX endpoints through server-side configuration if possible, although this is often difficult in dynamic WordPress environments where plugins define their own routes. Additionally, enforcing stricter user role policies can reduce the attack surface by limiting the number of accounts with even minimal write capabilities. It is also advisable to implement Web Application Firewall rules that monitor for anomalous patterns in AJAX request headers or payloads associated with book management functions, providing an additional layer of defense against automated exploitation attempts targeting this specific weakness.