# CVE-2020-36719: ListingPro - WordPress Directory & Listing Theme < 2.6.1 - Arbitrary Plugin Installation, Activation and Deactivation

> Unauthenticated attackers can install, activate, or deactivate arbitrary plugins due to missing capability checks in the ListingPro WordPress theme.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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-vpf4-7pch-f7ph

## What is CVE-2020-36719?

CVE-2020-36719 is a critical missing authorization vulnerability in ListingPro - WordPress Directory & Listing Theme, 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 ListingPro - WordPress Directory & Listing Theme for WordPress is vulnerable to Arbitrary Plugin Installation, Activation and Deactivation in versions before 2.6.1. This is due to a missing capability check on the lp_cc_addons_actions function. This makes it possible for unauthenticated attackers to arbitrarily install, activate and deactivate any plugin.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Cridio Listingpro.

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

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

## Is CVE-2020-36719 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-36719 exists.

Public exploit code:

- ListingPro < 2.6.1 - Arbitrary Plugin Installation/Activation/Deactivation (nuclei): http/cves/2020/CVE-2020-36719.yaml

## Other vulnerabilities in ListingPro - WordPress Directory & Listing Theme

- [CVE-2024-38795](https://insights.sbomify.com/CVE-2024-38795/): WordPress ListingPro plugin <= 2.9.4 - Unauthenticated SQL Injection vulnerability (critical 9.3)
- [CVE-2024-39622](https://insights.sbomify.com/CVE-2024-39622/): WordPress ListingPro theme <= 2.9.4 - Unauthenticated SQL Injection vulnerability (critical 9.3)
- [CVE-2024-39619](https://insights.sbomify.com/CVE-2024-39619/): WordPress ListingPro plugin <= 2.9.4 - Unauthenticated Local File Inclusion vulnerability (critical 9.0)
- [CVE-2024-39623](https://insights.sbomify.com/CVE-2024-39623/): WordPress ListingPro theme <= 2.9.4 - Cross Site Request Forgery (CSRF) to Account Takeover vulnerability (high 8.8)
- [CVE-2024-39620](https://insights.sbomify.com/CVE-2024-39620/): WordPress ListingPro plugin <= 2.9.4 - SQL Injection vulnerability (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36719 is a critical missing authorization vulnerability in ListingPro - WordPress Directory & Listing Theme, published on 7 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-36719 exists.

Affected product: ListingPro - WordPress Directory & Listing Theme. 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-36719/ (Markdown: https://insights.sbomify.com/CVE-2020-36719/index.md)
```

## Sources

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

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