# CVE-2021-24627: G Auto-Hyperlink <= 1.0.1 - Admin+ SQL Injection

> Authenticated attackers can inject SQL via the id parameter in the G Auto-Hyperlink WordPress plugin admin dashboard.

- **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:** 8 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-37r6-42gm-rcgg

## What is CVE-2021-24627?

CVE-2021-24627 is a high-severity SQL injection vulnerability in Unknown G Auto-Hyperlink, published on 8 Nov 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The G Auto-Hyperlink WordPress plugin through 1.0.1 does not sanitise or escape an 'id' GET parameter before using it in a SQL statement, to select data to be displayed in the admin dashboard, 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-24627?

It affects 1 product.


Products: G Auto-Hyperlink Project G Auto-Hyperlink.

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

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

## Is CVE-2021-24627 being exploited?

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

Public exploit code:

- G Auto-Hyperlink <= 1.0.1 - SQL Injection (nuclei): http/cves/2021/CVE-2021-24627.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24627 is a high-severity SQL injection vulnerability in Unknown G Auto-Hyperlink, published on 8 Nov 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-24627 exists.

Affected product: Unknown G Auto-Hyperlink. 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-24627/ (Markdown: https://insights.sbomify.com/CVE-2021-24627/index.md)
```

## Sources

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

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