# CVE-2021-24403: WordPress Page Contact <= 1.0 - Authenticated (editor+) SQL Injection

> Authenticated low-privilege users can exploit unsanitized input in the Orders functionality to perform SQL injection attacks.

- **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:** 20 Sep 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-hfq3-j248-m7rx

## What is CVE-2021-24403?

CVE-2021-24403 is a high-severity SQL injection vulnerability in Unknown WordPress Page Contact, published on 20 Sep 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Orders functionality in the WordPress Page Contact plugin through 1.0 has an order_id parameter which is not sanitised, escaped or validated before inserting to a SQL statement, leading to SQL injection. The feature is available to low privilege users such as contributors

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

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

It affects 1 product.


Products: Wpagecontact Project Wpagecontact.

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

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

## Is CVE-2021-24403 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24403 is a high-severity SQL injection vulnerability in Unknown WordPress Page Contact, published on 20 Sep 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-24403 in the wild and no public exploit code.

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

## Sources

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

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