# CVE-2013-5028: SQL injection in n/a

> Remote authenticated users can execute arbitrary SQL commands via search parameters in Kwok Information Server, potentially compromising data integrity and confidentiality.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cgc8-pffc-72mr

## What is CVE-2013-5028?

CVE-2013-5028 is a medium-severity SQL injection vulnerability in n/a, published on 11 Oct 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in IT/hardware-list.dll in Kwoksys Kwok Information Server before 2.8.5 allows remote authenticated users to execute arbitrary SQL commands via the (1) hardwareType, (2) hardwareStatus, or (3) hardwareLocation parameter in a search command.

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

## Which versions are affected by CVE-2013-5028?

It affects 1 product.


Products: Kwoksys Information Server.

## How do I fix CVE-2013-5028?

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

## Is CVE-2013-5028 being exploited?

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

Public exploit code:

- Kwok Information Server - Multiple SQL Injections (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2022-45326](https://insights.sbomify.com/CVE-2022-45326/): XML external entity in n/a (medium 4.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5028 and fix it if it is affected.

What it is: CVE-2013-5028 is a medium-severity SQL injection vulnerability in n/a, published on 11 Oct 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-5028 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-2013-5028/ (Markdown: https://insights.sbomify.com/CVE-2013-5028/index.md)
```

## Sources

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

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