# CVE-2021-24777: Hotscot Contact Form < 1.3 - Admin+ SQL Injection

> An authenticated admin can exploit unsanitized input in the view submission feature to perform SQL injection, allowing unauthorized database access.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9j9f-c66r-6h93

## What is CVE-2021-24777?

CVE-2021-24777 is a high-severity SQL injection vulnerability in Unknown Hotscot Contact Form, published on 7 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The view submission functionality in the Hotscot Contact Form WordPress plugin before 1.3 makes a get request with the sub_id parameter which not sanitised, escaped or validated before inserting to a SQL statement, leading to an SQL injection.

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

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

It affects 1 product.


Products: Hotscot Contact Form.

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

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

## Is CVE-2021-24777 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24777 is a high-severity SQL injection vulnerability in Unknown Hotscot Contact Form, published on 7 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-24777 in the wild and no public exploit code.

Affected product: Unknown Hotscot Contact Form. 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-24777/ (Markdown: https://insights.sbomify.com/CVE-2021-24777/index.md)
```

## Sources

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

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