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

> SQL injection in search scripts allows attackers to manipulate database queries, potentially exposing or modifying real estate data.

- **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:** 31 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4gqr-8qrv-76vw

## What is CVE-2017-15991?

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

### Official description

Vastal I-Tech Agent Zone (aka The Real Estate Script) allows SQL Injection in searchCommercial.php via the property_type, city, or posted_by parameter, or searchResidential.php via the property_type, city, or bedroom parameter, a different vulnerability than CVE-2008-3951, CVE-2009-3497, and CVE-2012-0982.

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

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

It affects 1 product.


Products: Vastal Agent Zone.

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

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

## Is CVE-2017-15991 being exploited?

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

Public exploit code:

- Vastal I-Tech Agent Zone - 'searchCommercial.php' / 'searchResidential.php' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-0982](https://insights.sbomify.com/CVE-2012-0982/): SQL injection in n/a (high 7.5)
- [CVE-2009-3497](https://insights.sbomify.com/CVE-2009-3497/): SQL injection in n/a (high 7.5)
- [CVE-2008-3951](https://insights.sbomify.com/CVE-2008-3951/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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