# CVE-2020-36852: Custom Searchable Data Entry System <= 1.7.1 - Unauthenticated Database Wiping

> Unauthenticated attackers can wipe database tables due to missing capability checks in the Custom Searchable Data Entry System plugin.

- **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:** 1 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-9g2p-rm62-74m5

## What is CVE-2020-36852?

CVE-2020-36852 is a critical missing authorization vulnerability in ghazale Custom Searchable Data Entry System, published on 1 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Custom Searchable Data Entry System plugin for WordPress is vulnerable to unauthenticated database wiping in versions up to, and including 1.7.1, due to a missing capability check and lack of sufficient validation on the ghazale_sds_delete_entries_table_row() function. This makes it possible for unauthenticated attackers to completely wipe database tables such as wp_users.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2020-36852 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36852 is a critical missing authorization vulnerability in ghazale Custom Searchable Data Entry System, published on 1 Oct 2025. 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-36852 in the wild and no public exploit code.

Affected product: ghazale Custom Searchable Data Entry System. 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-36852/ (Markdown: https://insights.sbomify.com/CVE-2020-36852/index.md)
```

## Sources

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

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