# CVE-2020-36833: Indeed Membership Pro 7.3 - 8.6 - Missing Authorization Checks

> Authenticated attackers with minimal permissions can bypass authorization checks to modify settings and view sensitive data in the Indeed Membership Pro plugin.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2024
- **Updated:** 16 Oct 2024
- **Also known as:** GHSA-wqjf-7qxp-8hc8

## What is CVE-2020-36833?

CVE-2020-36833 is a medium-severity missing authorization vulnerability in wpindeed Indeed Membership Pro, published on 16 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Indeed Membership Pro plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on various AJAX actions in versions 7.3 - 8.6. This makes it possible for authenticated attacker, with minimal permission, such as a subscriber, to perform a variety of actions such as modifying settings and viewing sensitive data.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2020-36833 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36833 is a medium-severity missing authorization vulnerability in wpindeed Indeed Membership Pro, published on 16 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36833 in the wild and no public exploit code.

Affected product: wpindeed Indeed Membership Pro. 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-36833/ (Markdown: https://insights.sbomify.com/CVE-2020-36833/index.md)
```

## Sources

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

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