# CVE-2021-24631: Unlimited PopUps <= 4.5.3 - Author+ SQL Injection

> Authenticated attackers with editor privileges can exploit SQL injection in the Unlimited PopUps plugin to read or modify database contents.

- **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:** 8 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-xgj7-47qp-p88h

## What is CVE-2021-24631?

CVE-2021-24631 is a high-severity SQL injection vulnerability in Unknown Unlimited PopUps, published on 8 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Unlimited PopUps WordPress plugin through 4.5.3 does not sanitise or escape the did GET parameter before using it in a SQL statement, available to users as low as editor, leading to an authenticated SQL Injection

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

## Which versions are affected by CVE-2021-24631?

It affects 1 product.


Products: Unlimited Popups Project Unlimited Popups.

## How do I fix CVE-2021-24631?

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

## Is CVE-2021-24631 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24631 and fix it if it is affected.

What it is: CVE-2021-24631 is a high-severity SQL injection vulnerability in Unknown Unlimited PopUps, published on 8 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-24631 in the wild and no public exploit code.

Affected product: Unknown Unlimited PopUps. 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-2021-24631/ (Markdown: https://insights.sbomify.com/CVE-2021-24631/index.md)
```

## Sources

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

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