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

> Attackers can manipulate the database via SQL injection in the login page of the Restaurant Management System.

- **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:** 20 Oct 2025
- **Updated:** 20 Oct 2025
- **Also known as:** GHSA-qcw5-vqgm-rfg5

## What is CVE-2025-60783?

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

### Official description

There is a SQL injection vulnerability in Restaurant Management System DBMS Project v1.0 via login.php. The vulnerability allows attackers to manipulate the application's database through specially crafted SQL query strings.

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

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

It affects 1 product.


Products: Rajvi-Patel-22 Restaurant-Management-System-Dbms-Project.

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

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

## Is CVE-2025-60783 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60783 is a medium-severity SQL injection vulnerability in n/a, published on 20 Oct 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-60783 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-60783/ (Markdown: https://insights.sbomify.com/CVE-2025-60783/index.md)
```

## Sources

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

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