# CVE-2021-3018: SQL injection in n/a

> Unauthenticated attackers can perform Boolean-based SQL injection via the id parameter in ibexwebCMS to read database contents.

- **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:** 5 Jan 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-ww76-wxv4-qwxc

## What is CVE-2021-3018?

CVE-2021-3018 is a critical SQL injection vulnerability in n/a, published on 5 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ipeak Infosystems ibexwebCMS (aka IPeakCMS) 3.5 is vulnerable to an unauthenticated Boolean-based SQL injection via the id parameter on the /cms/print.php page.

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

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

It affects 1 product.


Products: Ipeak Ipeakcms.

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

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

## Is CVE-2021-3018 being exploited?

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

Public exploit code:

- IPeakCMS 3.5 - Boolean-based blind SQLi (exploitdb)
- IPeakCMS 3.5 - SQL Injection (nuclei): http/cves/2021/CVE-2021-3018.yaml

## Fix prompt for AI coding agents

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

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

## Sources

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

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