DiveBook
divebook · plugin
Known security vulnerabilities for DiveBook. Find out in seconds which version runs on your site with WP Lens.
3 known vulnerabilities
3 exploitable without logging in · latest Dec 8, 2020
Closed on wordpress.org
Removed from the directory on Dec 9, 2020 · reason: security issue. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Oct 14, 2026
Vulnerabilities
- Medium 6.1
CVE-2020-14206unauthenticated · needs a click
The DiveBook plugin 1.1.4 for WordPress is prone to unauthenticated XSS within the filter function (via an arbitrary parameter).
- Medium 5.3
CVE-2020-14207unauthenticated
The DiveBook plugin 1.1.4 for WordPress was prone to a SQL injection within divelog.php, allowing unauthenticated users to retrieve data fro
- Medium 5.3
CVE-2020-14205unauthenticated
The DiveBook plugin 1.1.4 for WordPress is prone to improper access control in the Log Dive form because it fails to perform authorization c
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).