# CVE-2020-14205: Missing authorization in n/a

> An attacker can manipulate dive log integrity in the DiveBook WordPress plugin due to missing authorization checks on the Log Dive form.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mjqr-j4x8-38w5

## What is CVE-2020-14205?

CVE-2020-14205 is a medium-severity missing authorization vulnerability in n/a, published on 8 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 checks. An attacker may leverage this issue to manipulate the integrity of dive logs.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2020-14205?

It affects 1 product.


Products: Divebook Project Divebook.

## How do I fix CVE-2020-14205?

No fix has been published for CVE-2020-14205 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-14205 being exploited?

There is no known exploitation of CVE-2020-14205 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-14206](https://insights.sbomify.com/CVE-2020-14206/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2020-14207](https://insights.sbomify.com/CVE-2020-14207/): SQL injection in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14205 and fix it if it is affected.

What it is: CVE-2020-14205 is a medium-severity missing authorization vulnerability in n/a, published on 8 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14205 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-14205/ (Markdown: https://insights.sbomify.com/CVE-2020-14205/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-14205
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-14205
- OSV: https://osv.dev/vulnerability/CVE-2020-14205

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-14205/
Summaries are generated and may contain mistakes; the official description above is the record.