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

> Blind SQL injection in Chop Slider 3 allows attackers to execute arbitrary SQL queries via the id parameter, risking database compromise.

- **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:** 8 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r26h-642q-j6cg

## What is CVE-2020-11530?

CVE-2020-11530 is a critical SQL injection vulnerability in n/a, published on 8 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A blind SQL injection vulnerability is present in Chop Slider 3, a WordPress plugin. The vulnerability is introduced in the id GET parameter supplied to get_script/index.php, and allows an attacker to execute arbitrary SQL queries in the context of the WP database user.

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

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

It affects 1 product.


Products: Idangero Chop Slider.

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

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

## Is CVE-2020-11530 being exploited?

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

Public exploit code:

- WordPress Plugin ChopSlider 3.4 - 'id' SQL Injection (exploitdb)
- WordPress ChopSlider3 id SQLi Scanner (metasploit)
- WordPress Chop Slider 3 - Blind SQL Injection (nuclei): http/cves/2020/CVE-2020-11530.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11530 is a critical SQL injection vulnerability in n/a, published on 8 May 2020. 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-11530 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-11530/ (Markdown: https://insights.sbomify.com/CVE-2020-11530/index.md)
```

## Sources

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

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