# CVE-2017-1000474: SQL injection in n/a

> SQL injection in multiple scripts allows attackers to steal credentials and execute remote code in the Vehicle Sales Management System.

- **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:** 24 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9mg8-wpmg-p8xr

## What is CVE-2017-1000474?

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

### Official description

Soyket Chowdhury Vehicle Sales Management System version 2017-07-30 is vulnerable to multiple SQL Injecting in login/vehicle.php, login/profile.php, login/Actions.php, login/manage_employee.php, and login/sell.php scripts resulting in the expose of user's login credentials, SQL Injection and Stored XSS vulnerability, which leads to remote code executing.

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

## Which versions are affected by CVE-2017-1000474?

It affects 1 product.


Products: Vehicle Sales Management System Project Vehicle Sales Management System.

## How do I fix CVE-2017-1000474?

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

## Is CVE-2017-1000474 being exploited?

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

Public exploit code:

- Vehicle Sales Management System - Multiple Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000474 and fix it if it is affected.

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

## Sources

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

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