# GHSA-w7q7-vjp8-7jv4: SQL Injection in typeorm

> Attackers can inject SQL statements via unvalidated field names in TypeORM, allowing arbitrary query execution and data manipulation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Jun 2019

## What is GHSA-w7q7-vjp8-7jv4?

GHSA-w7q7-vjp8-7jv4 is a SQL injection vulnerability in typeorm, published on 6 Jun 2019. It can be exploited over the network, with no action from the victim.

### Official description

Versions of `typeorm` before 0.1.15 are vulnerable to SQL Injection. Field names are not properly validated allowing attackers to inject SQL statements and execute arbitrary SQL queries.

## Recommendation

Upgrade to version 0.1.15

## Which versions are affected by GHSA-w7q7-vjp8-7jv4?

2 open source packages ship an affected version, including typeorm.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typeorm` | npm | All versions | 0.1.15 |
| `typeorm` | npm | All versions | 0.1.15 |

## How do I fix GHSA-w7q7-vjp8-7jv4?

Upgrade typeorm to 0.1.15 or later.

## Is GHSA-w7q7-vjp8-7jv4 being exploited?

There is no known exploitation of GHSA-w7q7-vjp8-7jv4 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-w7q7-vjp8-7jv4 and fix it if it is affected.

What it is: GHSA-w7q7-vjp8-7jv4 is a SQL injection vulnerability in typeorm, published on 6 Jun 2019. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-w7q7-vjp8-7jv4 in the wild and no public exploit code.

Affected packages and fixed versions:
- typeorm (npm): affected all versions; fixed in 0.1.15
- typeorm (npm): affected all versions; fixed in 0.1.15

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/GHSA-w7q7-vjp8-7jv4/ (Markdown: https://insights.sbomify.com/GHSA-w7q7-vjp8-7jv4/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-w7q7-vjp8-7jv4

---
From sbomify Insights: https://insights.sbomify.com/GHSA-w7q7-vjp8-7jv4/
Summaries are generated and may contain mistakes; the official description above is the record.