# CVE-2024-57178: SQL injection in n/a

> Attackers can inject SQL via the stock-symbol parameter to read user data or manipulate application behavior in Stock-Forecaster.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2025
- **Updated:** 10 Feb 2025
- **Also known as:** GHSA-6v8g-q77p-ghph

## What is CVE-2024-57178?

CVE-2024-57178 is a medium-severity SQL injection vulnerability in n/a, published on 10 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An SQL injection vulnerability exists in Stock-Forecaster <=01-04-2020. By sending a specially crafted 'stock-symbol' parameter to the portofolio() endpoint, it is possible to trigger an SQL injection in the application. As a result, the attacker will be able the user data or manipulate the software behavior.

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

## Which versions are affected by CVE-2024-57178?


## How do I fix CVE-2024-57178?

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

## Is CVE-2024-57178 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-57178 and fix it if it is affected.

What it is: CVE-2024-57178 is a medium-severity SQL injection vulnerability in n/a, published on 10 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-57178 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-2024-57178/ (Markdown: https://insights.sbomify.com/CVE-2024-57178/index.md)
```

## Sources

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

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