The Mooberry Book Manager WordPress plugin through 4.16.2 does not perform any capability or nonce check in one of its
Source GCVE Database
Not known to be exploited.
Data as of 22 Nov 2026, 07:27 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 22 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mooberry Book Manager | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict user roles that have access to the vulnerable AJAX action and consider disabling or limiting the plugin's functionality to trusted users only.
Description
The Mooberry Book Manager WordPress plugin through version 4.16.2 contains a vulnerability where one of its AJAX actions lacks capability and nonce checks. This flaw allows any authenticated user, including those with minimal roles such as Subscriber, to change the publisher assigned to any book, including those created by other users, and to create new book records. The absence of a nonce check also enables exploitation via Cross-Site Request Forgery (CSRF) against any logged-in user.