# CVE-2020-12104: SQL injection in n/a

> Authenticated attackers can execute arbitrary SQL commands via the Import feature in the wp-advanced-search WordPress plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 5 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mh87-x5p4-6j68

## What is CVE-2020-12104?

CVE-2020-12104 is a high-severity SQL injection vulnerability in n/a, published on 5 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Import feature in the wp-advanced-search plugin 3.3.6 for WordPress is vulnerable to authenticated SQL injection via an uploaded .sql file. An attacker can use this to execute SQL commands without any validation.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Internet-Formation Wp-Advanced-Search.

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

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

## Is CVE-2020-12104 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-9796](https://insights.sbomify.com/CVE-2024-9796/): WP-Advanced-Search < 3.3.9.2 - Unauthenticated SQL Injection (medium 5.9)
- [CVE-2022-47447](https://insights.sbomify.com/CVE-2022-47447/): WordPress WP-Advanced-Search Plugin <= 3.3.8 is vulnerable to Cross Site Request Forgery (CSRF) (medium 4.3)
- [CVE-2024-10554](https://insights.sbomify.com/CVE-2024-10554/): WP-Advanced-Search < 3.3.9.3 - Admin+ Stored XSS (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-12104 is a high-severity SQL injection vulnerability in n/a, published on 5 May 2020. 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-12104 in the wild and no public exploit code.

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

## Sources

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

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