DivebookWordPress extension · Divebook Project
CVE-2020-14207
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe DiveBook plugin 1.1.4 for WordPress was prone to a SQL injection within divelog.php, allowing unauthenticated users to retrieve data from the database via the divelog.php filter_diver parameter.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe DiveBook WordPress plugin version 1.1.4 contains an unauthenticated SQL injection vulnerability in divelog.php via the filter_diver parameter. Attackers can exploit this to inject malicious SQL queries and extract sensitive data from the WordPress database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
DivebookWordPress extension
= 1.1.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm DiveBook plugin is installedLocate the DiveBook plugin directory in the WordPress plugins folder (wp-content/plugins/) or check via WordPress admin dashboard under PluginsAffected if The DiveBook plugin is present in the WordPress installation
-
Identify the installed plugin versionOpen the main plugin file (usually divelog.php or plugin header file) and locate the version comment, or check the readme.txt file for the Version headerAffected if The installed version is 1.1.4
-
Verify the vulnerable file existsCheck for the presence of divelog.php in the plugin directory (wp-content/plugins/divebook/divelog.php or similar path)Affected if divelog.php exists in the plugin directory
-
Confirm the vulnerable parameter is acceptedReview the divelog.php source code for the filter_diver parameter handling, specifically looking for unsanitized use in SQL queries, or attempt a test request to the page with a filter_diver parameterAffected if The filter_diver parameter is processed without proper SQL sanitization in the code
A user is affected if DiveBook plugin version 1.1.4 is installed and the divelog.php file with the vulnerable filter_diver parameter is accessible and processes unsanitized SQL queries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to the latest version of the DiveBook plugin that addresses this vulnerability. If no patched version is available, remove the plugin until a fix is released. Consider implementing web application firewall rules as a temporary mitigation.
Fix this in Divebook
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14207 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-14207 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data