← WordPress Vulnerabilities
WordPress security by component

Mooberry Book Manager

Mooberry Book Manager manages book records, authors, genres, series, and related book information in WordPress.

Mooberry Book Manager (mooberry-book-manager) is a WordPress plugin with 2 published CVE records in this archive. The latest tracked vulnerability was published Oct 06, 2026; the highest published CVSS base score is 7.1.

Plugin slug: mooberry-book-manager

CVE-2026-32581: Mooberry Book Manager: SQL injection

The export requires the Subscriber role or higher. Attacker-controlled input can change database-query semantics and expose database contents. The vulnerable query, endpoint and parameter are undisclosed. The supplied vector reports high confidentiality impact, limited availability impact. The vector rates attack complexity as high; the extra prerequisite is undisclosed. The vector requires no victim interaction. Affected versions: 4.16.2. No fixed release is confirmed. The checked official release is 4.16.2; it does not establish a fixed version for this CVE.

PublishedOct 06, 2026
Safe version guidanceSee mitigation notes
Published vulnerabilities for mooberry-book-manager
Safe version
Oct 06, 2026 CVE-2026-32581
Mooberry Book Manager: SQL injection
The export requires the Subscriber role or higher. Attacker-controlled input can change database-query semantics and expose database contents. The vulnerable query, endpoint and parameter are undisclosed. The supplied vector reports high confidentiality impact, limited availability impact. The vector rates attack complexity as high; the extra prerequisite is undisclosed. The vector requires no victim interaction. Affected versions: 4.16.2. No fixed release is confirmed. The checked official release is 4.16.2; it does not establish a fixed version for this CVE.
See mitigation notes
CVE7.1
NVDPending
May 06, 2024 CVE-2024-34368
Mooberry Book Manager: A security weakness
Mooberry Book Manager is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE5.3
NVDPending