# CVE-2018-12498: SQL injection in n/a

> SQL injection in iCMS admin panel allows attackers to read or modify database contents via the id parameter.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 15 Jun 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-cpxm-c53h-qwrq

## What is CVE-2018-12498?

CVE-2018-12498 is a critical SQL injection vulnerability in n/a, published on 15 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

spider.admincp.php in iCMS v7.0.8 has SQL Injection via the id parameter in an app=spider&do=batch request to admincp.php.

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

## Which versions are affected by CVE-2018-12498?

It affects 1 product.


Products: Icmsdev Icms.

## How do I fix CVE-2018-12498?

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

## Is CVE-2018-12498 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-42322](https://insights.sbomify.com/CVE-2023-42322/): Information disclosure in n/a (critical 9.8)
- [CVE-2019-6259](https://insights.sbomify.com/CVE-2019-6259/): SQL injection in n/a (critical 9.8)
- [CVE-2018-18702](https://insights.sbomify.com/CVE-2018-18702/): SQL injection in n/a (critical 9.8)
- [CVE-2018-14514](https://insights.sbomify.com/CVE-2018-14514/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2018-9924](https://insights.sbomify.com/CVE-2018-9924/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12498 and fix it if it is affected.

What it is: CVE-2018-12498 is a critical SQL injection vulnerability in n/a, published on 15 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-12498 in the wild and no public exploit code.

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-2018-12498/ (Markdown: https://insights.sbomify.com/CVE-2018-12498/index.md)
```

## Sources

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

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