# CVE-2025-57254: SQL injection in n/a

> Remote attackers can execute arbitrary SQL queries via unsanitized login parameters, leading to unauthorized access and exposure of sensitive medical data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2025
- **Updated:** 1 Oct 2025
- **Also known as:** GHSA-j4g5-gmc2-6cfx

## What is CVE-2025-57254?

CVE-2025-57254 is a medium-severity SQL injection vulnerability in n/a, published on 30 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An SQL injection vulnerability in user-login.php and index.php of Karthikg1908 Hospital Management System (HMS) 1.0 allows remote attackers to execute arbitrary SQL queries via the username and password POST parameters. The application fails to properly sanitize input before embedding it into SQL queries, leading to unauthorized access or potential data breaches. This can result in privilege escalation, account takeover, or exposure of sensitive medical data.

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

## Which versions are affected by CVE-2025-57254?


## How do I fix CVE-2025-57254?

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

## Is CVE-2025-57254 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-57254 and fix it if it is affected.

What it is: CVE-2025-57254 is a medium-severity SQL injection vulnerability in n/a, published on 30 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57254 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-2025-57254/ (Markdown: https://insights.sbomify.com/CVE-2025-57254/index.md)
```

## Sources

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

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