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

> Unauthenticated attackers can wipe the database due to missing authentication checks in the reset wizard actions hook.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 5 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3q59-p3w9-wv54

## What is CVE-2020-36333?

CVE-2020-36333 is a critical missing authorization vulnerability in n/a, published on 5 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

themegrill-demo-importer before 1.6.2 does not require authentication for wiping the database, because of a reset_wizard_actions hook.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Themegrill Themegrill Demo Importer.

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

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

## Is CVE-2020-36333 being exploited?

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

Public exploit code:

- ThemeGrill Demo Importer < 1.6.2 - Database Reset (nuclei): http/cves/2020/CVE-2020-36333.yaml

## Other vulnerabilities in n/a

- [CVE-2020-36334](https://insights.sbomify.com/CVE-2020-36334/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36333 is a critical missing authorization vulnerability in n/a, published on 5 May 2021. 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-36333 exists.

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-36333/ (Markdown: https://insights.sbomify.com/CVE-2020-36333/index.md)
```

## Sources

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

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