# CVE-2020-36716: WP Activity Log <= 4.0.1 - Missing Authorization

> Unauthenticated attackers can bypass authorization to run the setup wizard and access plugin configuration options in WP Activity Log.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-p8fg-fxjr-7v2x

## What is CVE-2020-36716?

CVE-2020-36716 is a high-severity missing authorization vulnerability in melapress WP Activity Log, published on 7 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Activity Log plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the setup_page function in versions up to, and including, 4.0.1. This makes it possible for unauthenticated attackers to run the setup wizard (if it has not been run previously) and access plugin configuration options.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Wpwhitesecurity Wp Activity Log.

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

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

## Is CVE-2020-36716 being exploited?

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

## Other vulnerabilities in melapress WP Activity Log

- [CVE-2023-2261](https://insights.sbomify.com/CVE-2023-2261/): WP Activity Log <= 4.5.0 - Missing Capabilities Check to User Enumeration (medium 4.3)
- [CVE-2023-2284](https://insights.sbomify.com/CVE-2023-2284/): WP Activity Log Premium <= 4.5.0 - Missing Authorization via ajax_switch_db (medium 4.3)
- [CVE-2023-2285](https://insights.sbomify.com/CVE-2023-2285/): WP Activity Log Premium <= 4.5.0 - Cross-Site Request Forgery via ajax_switch_db (medium 4.3)
- [CVE-2023-2286](https://insights.sbomify.com/CVE-2023-2286/): WP Activity Log <= 4.5.0 - Cross-Site Request Forgery via ajax_run_cleanup (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36716 is a high-severity missing authorization vulnerability in melapress WP Activity Log, published on 7 Jun 2023. 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-36716 in the wild and no public exploit code.

Affected product: melapress WP Activity Log. 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-36716/ (Markdown: https://insights.sbomify.com/CVE-2020-36716/index.md)
```

## Sources

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

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